| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20130802225036.GA29458@kroah.com> Date: Sat, 3 Aug 2013 06:50:36 +0800 From: Greg KH <gregkh@...uxfoundation.org> To: Joe Perches <joe@...ches.com> Cc: Srinivas Pandruvada <srinivas.pandruvada@...ux.intel.com>, linux-kernel@...r.kernel.org Subject: Re: [RFC v01 0/3] Power Capping Framework On Fri, Aug 02, 2013 at 03:33:26PM -0700, Joe Perches wrote: > On Sat, 2013-08-03 at 06:30 +0800, Greg KH wrote: > > On Fri, Aug 02, 2013 at 11:08:49AM -0700, Srinivas Pandruvada wrote: > > > Once this framework is approved, we will submit a RAPL client driver using this > > > framework. > > > > Also, given that you work with a lot of kernel developers, I would like > > to see their review and signed-off-by: on these patches before you > > resend them, please. That way I know that they agree with this > > framework as a way for their future changes in this area. > > Before is a bit hard on public mailing lists isn't it? That's implying that Intel doesn't have internal mailing lists where kernel patches are reviewed and proposed before being made public... > Shouldn't the reviewed-by/acked-by/signed-off-by's be > done after a real patch is submitted? That's fine too, but then the needed people need to be cc:ed. thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists