From: Greg KH <gregkh@linuxfoundation.org>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: stable@vger.kernel.org, stable-commits@vger.kernel.org,
zhangshida@kylinos.cn, Coly Li <colyli@fnnas.com>
Subject: Re: Patch "bcache: fix improper use of bi_end_io" has been added to the 6.6-stable tree
Date: Thu, 15 Jan 2026 12:40:49 +0100 [thread overview]
Message-ID: <2026011537-visiting-fastness-a184@gregkh> (raw)
In-Reply-To: <2026011517-apricot-supply-051c@gregkh>
On Thu, Jan 15, 2026 at 12:39:34PM +0100, Greg KH wrote:
> On Thu, Jan 15, 2026 at 03:47:39AM -0500, Kent Overstreet wrote:
> > On Mon, Jan 12, 2026 at 12:23:45PM -0500, Sasha Levin wrote:
> > > This is a note to let you know that I've just added the patch titled
> > >
> > > bcache: fix improper use of bi_end_io
> > >
> > > to the 6.6-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:
> > > bcache-fix-improper-use-of-bi_end_io.patch
> > > and it can be found in the queue-6.6 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.
> >
> > Sasha, has this been dropped?
>
> Why just drop it from 6.6? What about all other branches? What about
> Linus's tree?
Ah, it's being reverted there, ok, I'll go drop this from all branches
now, thanks.
greg k-h
prev parent reply other threads:[~2026-01-15 11:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260112172345.800703-1-sashal@kernel.org>
2026-01-12 17:34 ` Patch "bcache: fix improper use of bi_end_io" has been added to the 6.6-stable tree Kent Overstreet
2026-01-12 18:01 ` Kent Overstreet
2026-01-13 6:08 ` Coly Li
2026-01-13 6:21 ` Kent Overstreet
2026-01-15 8:47 ` Kent Overstreet
2026-01-15 11:39 ` Greg KH
2026-01-15 11:40 ` 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=2026011537-visiting-fastness-a184@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=colyli@fnnas.com \
--cc=kent.overstreet@linux.dev \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=zhangshida@kylinos.cn \
/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.