From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: linux-stable <stable@vger.kernel.org>,
Sasha Levin <sashal@kernel.org>,
TRINH-THAI Florent <florent.trinh-thai@csgroup.eu>
Subject: Re: All stable branches: apply fc96ec826bce ("spi: fsl-cpm: Use 16 bit mode for large transfers with even size")
Date: Mon, 15 May 2023 14:29:45 +0200 [thread overview]
Message-ID: <2023051508-affront-frantic-00be@gregkh> (raw)
In-Reply-To: <2023051534-portable-scarecrow-ec3c@gregkh>
On Mon, May 15, 2023 at 02:18:09PM +0200, Greg Kroah-Hartman wrote:
> On Sun, May 14, 2023 at 09:17:08AM +0000, Christophe Leroy wrote:
> > Hello,
> >
> > In addition to c20c57d9868d ("spi: fsl-spi: Fix CPM/QE mode Litte
> > Endian") that you already applied to all stable branches, could you
> > please also apply:
> >
> > 8a5299a1278e ("spi: fsl-spi: Re-organise transfer bits_per_word adaptation")
> > fc96ec826bce ("spi: fsl-cpm: Use 16 bit mode for large transfers with
> > even size")
> >
> > For 4.14 and 4.19, as prerequisit you will also need
> >
> > af0e6242909c ("spi: spi-fsl-spi: automatically adapt bits-per-word in
> > cpu mode")
>
> That commit did not apply to 4.14 or 4.19, so I did not apply any of
> these to those queues. Please provide working backports for those trees
> if you wish to see them there.
>
> The other trees all got the 2 commits queued up now, thanks.
Wait, no, these broke the build in 5.10.y and 5.4.y, did they work for
you? I've dropped them from there, let me see if 5.15.y builds...
Nope, 5.15.y breaks as well, so dropped from there.
thanks,
greg k-h
next prev parent reply other threads:[~2023-05-15 12:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-14 9:17 All stable branches: apply fc96ec826bce ("spi: fsl-cpm: Use 16 bit mode for large transfers with even size") Christophe Leroy
2023-05-15 12:18 ` Greg Kroah-Hartman
2023-05-15 12:29 ` Greg Kroah-Hartman [this message]
2023-05-15 12:29 ` Christophe Leroy
2023-05-15 12:33 ` Greg Kroah-Hartman
2023-05-15 14:25 ` Christophe Leroy
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=2023051508-affront-frantic-00be@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=christophe.leroy@csgroup.eu \
--cc=florent.trinh-thai@csgroup.eu \
--cc=sashal@kernel.org \
--cc=stable@vger.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