From: "Vaittinen, Matti" <Matti.Vaittinen@fi.rohmeurope.com>
To: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Cc: "mazziesaccount@gmail.com" <mazziesaccount@gmail.com>,
"sashal@kernel.org" <sashal@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"lee.jones@linaro.org" <lee.jones@linaro.org>,
"alexandre.belloni@bootlin.com" <alexandre.belloni@bootlin.com>
Subject: Re: [PATCH] mfd: bd70528: Fix hour register mask
Date: Fri, 17 Jan 2020 08:06:35 +0000 [thread overview]
Message-ID: <b5835b0fe842a01888d66c07281e13fc64c2c9ef.camel@fi.rohmeurope.com> (raw)
In-Reply-To: <20200117075714.GA1822218@kroah.com>
On Fri, 2020-01-17 at 08:57 +0100, gregkh@linuxfoundation.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
next prev parent reply other threads:[~2020-01-17 8:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-15 8:29 [PATCH] mfd: bd70528: Fix hour register mask Matti Vaittinen
2020-01-17 7:44 ` Vaittinen, Matti
2020-01-17 7:57 ` gregkh
2020-01-17 8:06 ` Vaittinen, Matti [this message]
2020-01-17 10:10 ` Lee Jones
2020-01-17 10:11 ` Vaittinen, Matti
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b5835b0fe842a01888d66c07281e13fc64c2c9ef.camel@fi.rohmeurope.com \
--to=matti.vaittinen@fi.rohmeurope.com \
--cc=alexandre.belloni@bootlin.com \
--cc=gregkh@linuxfoundation.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mazziesaccount@gmail.com \
--cc=sashal@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).