public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Qu Wenruo <wqu@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 4/4] btrfs: make submit_one_bio() to return void
Date: Mon, 11 Apr 2022 14:23:24 +0200	[thread overview]
Message-ID: <YlQdvFjBq8ESu3Yz@kroah.com> (raw)
In-Reply-To: <YlQb9pH6dQ1zL8ix@infradead.org>

On Mon, Apr 11, 2022 at 05:15:50AM -0700, Christoph Hellwig wrote:
> On Mon, Apr 11, 2022 at 03:20:47PM +0800, Qu Wenruo wrote:
> > > This really should go into patch 1.
> > > 
> > Stable tree won't be happy about the size.
> 
> Really?  I've never really seen stable maintainers complain about
> the size of a patch.  Especially if it is almost 100% removal of buggy
> code.

That sounds like a great patch to take for stable kernels :)

  reply	other threads:[~2022-04-11 12:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-11  6:12 [PATCH 0/4] btrfs: vairous bug fixes related to generic/475 failure with subpage cases Qu Wenruo
2022-04-11  6:12 ` [PATCH 1/4] btrfs: avoid double clean up when submit_one_bio() failed Qu Wenruo
2022-04-11  7:14   ` Christoph Hellwig
2022-04-11  7:15     ` Qu Wenruo
2022-04-11  7:19       ` Christoph Hellwig
2022-04-11  7:35         ` Qu Wenruo
2022-04-11  6:12 ` [PATCH 2/4] btrfs: fix the error handling for submit_extent_page() for btrfs_do_readpage() Qu Wenruo
2022-04-11  7:18   ` Christoph Hellwig
2022-04-11  7:31     ` Qu Wenruo
2022-04-11  6:12 ` [PATCH 3/4] btrfs: return correct error number for __extent_writepage_io() Qu Wenruo
2022-04-11  6:12 ` [PATCH 4/4] btrfs: make submit_one_bio() to return void Qu Wenruo
2022-04-11  7:18   ` Christoph Hellwig
2022-04-11  7:20     ` Qu Wenruo
2022-04-11 12:15       ` Christoph Hellwig
2022-04-11 12:23         ` Greg KH [this message]
2022-04-11 12:29           ` Qu Wenruo

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=YlQdvFjBq8ESu3Yz@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=hch@infradead.org \
    --cc=linux-btrfs@vger.kernel.org \
    --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