From: Greg KH <greg@kroah.com>
To: David Sterba <dsterba@suse.com>
Cc: stable@vger.kernel.org, Qu Wenruo <wqu@suse.com>,
Julian Taylor <julian.taylor@1und1.de>,
Sweet Tea Dorminy <sweettea-kernel@dorminy.me>,
Filipe Manana <fdmanana@suse.com>
Subject: Re: [PATCH 6.6.x] btrfs: do not wait for short bulk allocation
Date: Wed, 15 May 2024 09:22:24 +0200 [thread overview]
Message-ID: <2024051514-outline-phrase-df66@gregkh> (raw)
In-Reply-To: <20240514171225.11774-1-dsterba@suse.com>
On Tue, May 14, 2024 at 07:12:24PM +0200, David Sterba wrote:
> From: Qu Wenruo <wqu@suse.com>
>
> commit 1db7959aacd905e6487d0478ac01d89f86eb1e51 upstream.
Both now quued up, thanks,
greg k-h
prev parent reply other threads:[~2024-05-15 7:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-14 17:12 [PATCH 6.6.x] btrfs: do not wait for short bulk allocation David Sterba
2024-05-15 7:22 ` 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=2024051514-outline-phrase-df66@gregkh \
--to=greg@kroah.com \
--cc=dsterba@suse.com \
--cc=fdmanana@suse.com \
--cc=julian.taylor@1und1.de \
--cc=stable@vger.kernel.org \
--cc=sweettea-kernel@dorminy.me \
--cc=wqu@suse.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).