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:   Fri, 17 Jan 2020 08:06:35 +0000
From:   "Vaittinen, Matti" <Matti.Vaittinen@...rohmeurope.com>
To:     "gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>
CC:     "mazziesaccount@...il.com" <mazziesaccount@...il.com>,
        "sashal@...nel.org" <sashal@...nel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "lee.jones@...aro.org" <lee.jones@...aro.org>,
        "alexandre.belloni@...tlin.com" <alexandre.belloni@...tlin.com>
Subject: Re: [PATCH] mfd: bd70528: Fix hour register mask


On Fri, 2020-01-17 at 08:57 +0100, gregkh@...uxfoundation.org wrote:
> On Fri, Jan 17, 2020 at 07:44:07AM +0000, Vaittinen, Matti wrote:
> > 
> > Is it possible to get this in 5.4 stable - while leaving this out
> > of
> > current MFD tree and applying the BD71828 series to MFD?
> 
> We only take patches that are in Linus's tree for the stable tree,
> unless there are very big reasons not to do so (i.e. it is totally
> rewritten in a different way there.)
> 
> Once the change/fix is in Linus's tree, then you can backport it to
> stable in a different way if you want, but you need to give lots of
> reasons why it is done that way.

Right. Thanks for the explanation Greg. I have no _strong_ reasons -
which means I'll split the RTC support patch in BD71828 series into two
- first of the patches being this fix, second being the BD71828
support. Then this fix can be taken in 5.4 after it has been merged to
Linus' tree - the BD71828 support can be omitted from 5.4

I hope the BD71828 series could still make it to next release - but if
it wont, then it might be in next after that :]

Lee, please skip this one, I'll do v10 of the BD71828 series where this
fix is included as separate fix-patch.

Regards
	Matti

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ