From: Greg KH <gregkh@linuxfoundation.org>
To: Matthew Wilcox <willy@infradead.org>
Cc: akpm@linux-foundation.org, balbirs@nvidia.com,
hannes@cmpxchg.org, hch@lst.de, mhocko@suse.com,
muchun.song@linux.dev, roman.gushchin@linux.dev,
shakeel.butt@linux.dev, stable@vger.kernel.org, urezki@gmail.com
Subject: Re: FAILED: patch "[PATCH] vmalloc: fix accounting with i915" failed to apply to 5.10-stable tree
Date: Tue, 21 Jan 2025 14:19:18 +0100 [thread overview]
Message-ID: <2025012101-mashing-unlinked-86c0@gregkh> (raw)
In-Reply-To: <Z3_y2-mV3eSWmqYQ@casper.infradead.org>
On Thu, Jan 09, 2025 at 04:01:31PM +0000, Matthew Wilcox wrote:
> On Mon, Dec 23, 2024 at 08:20:43PM +0000, Matthew Wilcox wrote:
> > On Mon, Dec 23, 2024 at 11:18:01AM +0100, gregkh@linuxfoundation.org wrote:
> > >
> > > The patch below does not apply to the 5.10-stable tree.
> > > If someone wants it applied there, or to any other stable or longterm
> > > tree, then please email the backport, including the original git commit
> > > id to <stable@vger.kernel.org>.
> >
> > The 5.15 patch also applies to the 5.10-stable tree. Thanks,
>
> Seems to have been missed? The 5.15 patch made it into 5.15.176
> but the 5.10 patch isn't in 5.10.233 released the same day.
>
Odd, don't know what happened there, sorry. Now queued up for the next
5.10.y release.
thanks,
greg "drowning in backports" k-h
prev parent reply other threads:[~2025-01-21 13:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-23 10:18 FAILED: patch "[PATCH] vmalloc: fix accounting with i915" failed to apply to 5.10-stable tree gregkh
2024-12-23 20:20 ` Matthew Wilcox
2025-01-09 16:01 ` Matthew Wilcox
2025-01-21 13:19 ` 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=2025012101-mashing-unlinked-86c0@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=balbirs@nvidia.com \
--cc=hannes@cmpxchg.org \
--cc=hch@lst.de \
--cc=mhocko@suse.com \
--cc=muchun.song@linux.dev \
--cc=roman.gushchin@linux.dev \
--cc=shakeel.butt@linux.dev \
--cc=stable@vger.kernel.org \
--cc=urezki@gmail.com \
--cc=willy@infradead.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