All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
	stable@vger.kernel.org
Subject: Re: suggest 00b80ac93553 ("spi: imx: mx51-ecspi: Move some initialisation to prepare_message hook.") for stable backports
Date: Fri, 21 Dec 2018 19:06:47 -0500	[thread overview]
Message-ID: <20181222000647.GI86645@sasha-vm> (raw)
In-Reply-To: <20181220145531.GA9325@sirena.org.uk>

On Thu, Dec 20, 2018 at 02:55:31PM +0000, Mark Brown wrote:
>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.

I'll happily take your backport here and an ack on it from Mark :)

--
Thanks,
Sasha

  reply	other threads:[~2018-12-22  0:06 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
2018-12-22  0:06   ` Sasha Levin [this message]
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=20181222000647.GI86645@sasha-vm \
    --to=sashal@kernel.org \
    --cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.