From: Greg KH <gregkh@linuxfoundation.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: stable@vger.kernel.org, stable-commits@vger.kernel.org,
Lyude Paul <lyude@redhat.com>, Danilo Krummrich <dakr@kernel.org>,
Dave Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>
Subject: Re: Patch "drm/nouveau: check ioctl command codes better" has been added to the 6.15-stable tree
Date: Mon, 21 Jul 2025 15:52:40 +0200 [thread overview]
Message-ID: <2025072129-severity-defame-164e@gregkh> (raw)
In-Reply-To: <b32c7957-6827-45a5-860b-f28baedd9f60@app.fastmail.com>
On Mon, Jul 21, 2025 at 03:14:50PM +0200, Arnd Bergmann wrote:
> On Mon, Jul 21, 2025, at 14:49, Sasha Levin wrote:
> > This is a note to let you know that I've just added the patch titled
> >
> > drm/nouveau: check ioctl command codes better
> >
> > to the 6.15-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:
> > drm-nouveau-check-ioctl-command-codes-better.patch
> > and it can be found in the queue-6.15 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.
>
> I got a regression report for this patch today, please don't backport
> it yet.
Dropped from both queues, thanks.
greg k-h
prev parent reply other threads:[~2025-07-21 13:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250721124923.811224-1-sashal@kernel.org>
2025-07-21 13:14 ` Patch "drm/nouveau: check ioctl command codes better" has been added to the 6.15-stable tree Arnd Bergmann
2025-07-21 13:52 ` 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=2025072129-severity-defame-164e@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=airlied@gmail.com \
--cc=arnd@arndb.de \
--cc=dakr@kernel.org \
--cc=lyude@redhat.com \
--cc=simona@ffwll.ch \
--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 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.