From: David Lechner <dlechner@baylibre.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, stable-commits@vger.kernel.org,
"Michael Hennerich" <michael.hennerich@analog.com>,
"Nuno Sá" <nuno.sa@analog.com>, "Mark Brown" <broonie@kernel.org>
Subject: Re: Patch "spi: axi-spi-engine: fix version format string" has been added to the 6.1-stable tree
Date: Mon, 13 May 2024 09:44:53 -0500 [thread overview]
Message-ID: <CAMknhBGNeK51xdcMpRNQ1eRnLrLQFY9dVYFL2LjsL5Gj+nQiSg@mail.gmail.com> (raw)
In-Reply-To: <2024051357-jimmy-smasher-0359@gregkh>
On Mon, May 13, 2024 at 7:54 AM Greg KH <gregkh@linuxfoundation.org> wrote:
>
> On Mon, May 06, 2024 at 03:47:02PM -0500, David Lechner wrote:
> > On 5/6/24 2:30 PM, Sasha Levin wrote:
> > > This is a note to let you know that I've just added the patch titled
> > >
> > > spi: axi-spi-engine: fix version format string
> > >
> > > to the 6.1-stable tree which can be found at:
> > > http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> > >
> > > The filename of the patch is:
> > > spi-axi-spi-engine-fix-version-format-string.patch
> > > and it can be found in the queue-6.1 subdirectory.
> > >
> > > If you, or anyone else, feels it should not be added to the stable tree,
> > > please let <stable@vger.kernel.org> know about it.
> > >
> > >
> >
> > Does not meet the criteria for stable.
> >
> > (only fixes theoretical problem, not actual documented problem)
>
> It fixes a real problem, incorrect data to userspace, why wouldn't you
> want it applied?
>
As discussed in the other thread, if you prefer to take this patch and
all of it's dependencies to keep things as close to mainline as
possible, I guess that is fine.
prev parent reply other threads:[~2024-05-13 14:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240506193025.272042-1-sashal@kernel.org>
2024-05-06 20:47 ` Patch "spi: axi-spi-engine: fix version format string" has been added to the 6.1-stable tree David Lechner
2024-05-13 12:54 ` Greg KH
2024-05-13 14:44 ` David Lechner [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=CAMknhBGNeK51xdcMpRNQ1eRnLrLQFY9dVYFL2LjsL5Gj+nQiSg@mail.gmail.com \
--to=dlechner@baylibre.com \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=michael.hennerich@analog.com \
--cc=nuno.sa@analog.com \
--cc=stable-commits@vger.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).