Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1500595
| From | "Rafael J. Wysocki" <rjw@rjwysocki.net> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH] cpufreq: intel_pstate: Add Knights Mill CPUID |
| Date | 2016-10-13 23:50 +0200 |
| Message-ID | <srW30-AS-3@gated-at.bofh.it> (permalink) |
| References | <srwBA-8aY-25@gated-at.bofh.it> <srxHj-sw-15@gated-at.bofh.it> <srPux-4ML-5@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
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
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
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
csiph-web