[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1476369859.27971.11.camel@intel.com>
Date: Thu, 13 Oct 2016 14:48:28 +0000
From: "Luc, Piotr" <Piotr.Luc@...el.com>
To: "rjw@...ysocki.net" <rjw@...ysocki.net>
CC: "srinivas.pandruvada@...ux.intel.com"
<srinivas.pandruvada@...ux.intel.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"viresh.kumar@...aro.org" <viresh.kumar@...aro.org>,
"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
"lenb@...nel.org" <lenb@...nel.org>
Subject: Re: [PATCH] cpufreq: intel_pstate: Add Knights Mill CPUID
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?
Thanks,
Piotr
Powered by blists - more mailing lists