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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 19 Jan 2016 10:15:45 -0800
From:	Daniel Kurtz <djkurtz@...omium.org>
To:	Greg KH <gregkh@...uxfoundation.org>
Cc:	Srinivas Kandagatla <srinivas.kandagatla@...aro.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Maxime Ripard <maxime.ripard@...e-electrons.com>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	Andrew-CT Chen <andrew-ct.chen@...iatek.com>,
	ariel@...guardiasur.com.ar, Sascha Hauer <s.hauer@...gutronix.de>,
	Eduardo Valentin <edubezval@...il.com>,
	Javi Merino <javi.merino@....com>, linux-pm@...r.kernel.org
Subject: Re: [PATCH 0/4] nvmem: new drivers for v4.5

Hi Greg,

On Mon, Jan 11, 2016 at 10:30 AM, Greg KH <gregkh@...uxfoundation.org> wrote:
>
> On Mon, Jan 11, 2016 at 01:21:44PM +0000, Srinivas Kandagatla wrote:
> >
> >
> > On 07/12/15 10:56, Srinivas Kandagatla wrote:
> > >Hi Greg,
> > >
> > >Here are 2 new nvmem drivers which are in the mailing list for long time
> > >and are good to go for some testing and find its way to v4.5-rc*.
> > >
> > >Could you please take these patches via char-misc tree.
> > Hi Greg,
> >
> > I have not seen these patches or https://lkml.org/lkml/2015/12/14/169 appear
> > in your char-misc tree/linux-next.
> >
> > Just wanted to know whats your plan on these patches?
>
> To wait until after 4.5-rc1 is out, sorry, my patch backlog got huge
> during Nov/Dec due to other external issues, I'll be digging out from
> them after 4.5-rc1 is out.

Soon after 4.5-rc1 sounds great.

FYI, to add some context, the Mediatek nvmem driver is actually
blocking several other drivers that we would also like to see land in
v4.5:  Mediatek thermal, Mediatek cpufreq_thermal, and Mediatek
devfreq_thermal.

So, the sooner nvmem lands, the earlier we can start staging/pushing
through the rest.

Thanks,
-Dan

>
> thanks,
>
> greg k-h

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ