From: Mark Brown <broonie@kernel.org>
To: William Kennington <william@wkennington.com>
Cc: avifishman70@gmail.com, joel@jms.id.au,
linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org,
tali.perry1@gmail.com, tmaimon77@gmail.com
Subject: Re: [PATCH] spi: npcm-fiu: Fix UMA reads when dummy.nbytes == 0
Date: Mon, 9 Oct 2023 23:52:41 +0100 [thread overview]
Message-ID: <ac0f55e5-e78c-42d6-a262-d0cef0bc0629@sirena.org.uk> (raw)
In-Reply-To: <CAD_4BXgMp5-gdsmzbCsWu7Xn+cFC=pwRf=YvNDSK0mDP=se0fQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 737 bytes --]
On Mon, Oct 09, 2023 at 03:39:43PM -0700, William Kennington wrote:
> > All being well this means that it will be integrated into the linux-next
> > tree (usually sometime in the next 24 hours) and sent to Linus during
> > the next merge window (or sooner if it is a bug fix), however if
> > problems are discovered then the patch may be dropped or
> Should I have marked this as a fix? I realized this after the fact but I
> need this backported to stable tree in order for my spi device to not crash
> the kernel.
Yes, although given the way stable picks things up there's a good chance
they'll grab it anyway based on the changelog. You can mail the stable
maintainers and ask for a backport once it hits Linus' tree to make
sure.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2023-10-09 22:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-22 18:28 William A. Kennington III
2023-10-02 15:41 ` Mark Brown
[not found] ` <CAD_4BXgMp5-gdsmzbCsWu7Xn+cFC=pwRf=YvNDSK0mDP=se0fQ@mail.gmail.com>
2023-10-09 22:52 ` Mark Brown [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=ac0f55e5-e78c-42d6-a262-d0cef0bc0629@sirena.org.uk \
--to=broonie@kernel.org \
--cc=avifishman70@gmail.com \
--cc=joel@jms.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=tali.perry1@gmail.com \
--cc=tmaimon77@gmail.com \
--cc=william@wkennington.com \
/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
all inboxes | Powered by JetHome®