public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "Zhang, Liyin (CN)" <liyin.zhang.cn@windriver.com>
Cc: stable@vger.kernel.org
Subject: Re: Backport request for two spi-nor otcal dtr odd length/address reads and writes patches to 6.12.y.
Date: Mon, 23 Mar 2026 10:29:11 +0100	[thread overview]
Message-ID: <2026032300-dictation-upper-71a6@gregkh> (raw)
In-Reply-To: <55ce141a-09fa-404a-9932-1e1d4b0ad034@windriver.com>

On Mon, Mar 23, 2026 at 03:53:09PM +0800, Zhang, Liyin (CN) wrote:
> Hi stable team,
> 
> Please consider applying the following mainlined patches to the 6.12.y
> stable tree:
> 
>   commit f156b23df6a84efb2f6686156be94d4988568954
>   "mtd: spi-nor: core: avoid odd length/address reads on 8D-8D-8D mode"
> 
>   commit 17926cd770ec837ed27d9856cf07f2da8dda4131
>   "mtd: spi-nor: core: avoid odd length/address writes in 8D-8D-8D mode"
> 
> Both patches are already present in mainline, 6.19, and 6.18.
> 
> Both patches fix the same class of bug: Octal DTR (8D-8D-8D) mode requires
> both the start address and transfer length to be even.
> And we actually encounter the same issues on different hardwares which
> supporting octal dtr in multiple earlier releases.
> 
> Now these two patches can be cleanly applied to 6.12 branch.
> Would you please help backport them to 6.12 first?

Now queued up, thanks.

greg k-h

      reply	other threads:[~2026-03-23  9:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-23  7:53 Backport request for two spi-nor otcal dtr odd length/address reads and writes patches to 6.12.y Zhang, Liyin (CN)
2026-03-23  9:29 ` Greg KH [this message]

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=2026032300-dictation-upper-71a6@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=liyin.zhang.cn@windriver.com \
    --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