From: Mark Brown <broonie@kernel.org>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: stable@vger.kernel.org
Subject: Re: suggest 00b80ac93553 ("spi: imx: mx51-ecspi: Move some initialisation to prepare_message hook.") for stable backports
Date: Thu, 20 Dec 2018 14:55:31 +0000 [thread overview]
Message-ID: <20181220145531.GA9325@sirena.org.uk> (raw)
In-Reply-To: <20181220144331.atc7g3d6eiilc4ut@pengutronix.de>
[-- Attachment #1: Type: text/plain, Size: 608 bytes --]
On Thu, Dec 20, 2018 at 03:43:31PM +0100, Uwe Kleine-König wrote:
> even though the subject sounds harmless it fixes a real bug.
> (Yes, I'm aware that commit isn't in Linus' tree yet, but I assume your
> tracking of patches targetting stable is better than mine, so I didn't
> wait :-)
> For backporting you also need its parent commit (i.e. e697271c4e29
> ("spi: imx: add a device specific prepare_message callback")). I have a
> local backport to v4.14 here which isn't entirely trivial. So just tell
> me if you need help.
This makes sense to me as a backport, an oversight on my part.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-12-20 14:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-20 14:43 suggest 00b80ac93553 ("spi: imx: mx51-ecspi: Move some initialisation to prepare_message hook.") for stable backports Uwe Kleine-König
2018-12-20 14:55 ` Mark Brown [this message]
2018-12-22 0:06 ` Sasha Levin
2018-12-23 21:21 ` [PATCH v4.14.x 1/2] spi: imx: add a device specific prepare_message callback Uwe Kleine-König
2018-12-23 21:21 ` [PATCH v4.14.x 2/2] spi: imx: mx51-ecspi: Move some initialisation to prepare_message hook Uwe Kleine-König
2018-12-27 20:56 ` Sasha Levin
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=20181220145531.GA9325@sirena.org.uk \
--to=broonie@kernel.org \
--cc=stable@vger.kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
/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).