From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: "Luc, Piotr" <Piotr.Luc@intel.com>
Cc: "srinivas.pandruvada@linux.intel.com"
<srinivas.pandruvada@linux.intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"viresh.kumar@linaro.org" <viresh.kumar@linaro.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"lenb@kernel.org" <lenb@kernel.org>
Subject: Re: [PATCH] cpufreq: intel_pstate: Add Knights Mill CPUID
Date: Thu, 13 Oct 2016 23:48:19 +0200 [thread overview]
Message-ID: <1780433.ynzyL9V08i@vostro.rjw.lan> (raw)
In-Reply-To: <1476369859.27971.11.camel@intel.com>
On Thursday, October 13, 2016 02:48:28 PM Luc, Piotr wrote:
> On Wed, 2016-10-12 at 21:39 +0200, Rafael J. Wysocki wrote:
> > On Wednesday, October 12, 2016 08:25:50 PM Piotr Luc wrote:
> > >
> > > ---
> > > Depends-on: x86/cpu/intel: Add Knights Mill to Intel family
> > > https://lkml.kernel.org/r/20161012180520.30976-1-piotr.luc () intel
> > > ! com
> >
> > First, putting broken URLs into patch tags doesn't really help.
>
> OK, with a series the link is not needed. I will refer to a patch
> inside the series.
>
> >
> > Second, please send all of these patches as a series where the first
> > patch makes the change the rest depends on. That would make them
> > easier to
> > handle.
> >
> I see. I just wonder if I should send the entire series to all
> maintainers that maintain individual modules/files or somehow limit
> 'TO' recipients only to their modules.
> Is any good method to it correctly?
The To: list should be possibly short. I would just send it To: x86@kernel.org
and put the other addresses into the CC list.
Generally speaking, CCs of the entire series should go to all of the relevant
maintainers (so they have a chance to respond to your patches in the context of
the series) though.
Thanks,
Rafael
prev parent reply other threads:[~2016-10-13 21:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-12 18:25 Piotr Luc
2016-10-12 19:39 ` Rafael J. Wysocki
2016-10-13 14:48 ` Luc, Piotr
2016-10-13 21:48 ` Rafael J. Wysocki [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1780433.ynzyL9V08i@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=Piotr.Luc@intel.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=viresh.kumar@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®