Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1500308 > unrolled thread

Re: [PATCH] cpufreq: intel_pstate: Add Knights Mill CPUID

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: [PATCH] cpufreq: intel_pstate: Add Knights Mill CPUID "Luc, Piotr" <Piotr.Luc@intel.com> - 2016-10-13 16:50 +0200
    Re: [PATCH] cpufreq: intel_pstate: Add Knights Mill CPUID "Rafael J. Wysocki" <rjw@rjwysocki.net> - 2016-10-13 23:50 +0200

#1500308 — 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

[toc] | [next] | [standalone]

#1500595

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

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web