linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Thumshirn <Johannes.Thumshirn@wdc.com>
To: "dsterba@suse.cz" <dsterba@suse.cz>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] btrfs: handle errors from async submission
Date: Fri, 31 Jul 2020 07:39:06 +0000	[thread overview]
Message-ID: <SN4PR0401MB3598FF781B4DE1120955FCDC9B4E0@SN4PR0401MB3598.namprd04.prod.outlook.com> (raw)
In-Reply-To: 20200730164657.GJ3703@twin.jikos.cz

On 30/07/2020 18:47, David Sterba wrote:
[...]
> The submit bio hooks have become a trivial indirect call to two
> functions, so we might get rid of the indirection eventually.

Yes that was my thought as well, but then I got distracted by more urgent
things again.

I'll add it to my backlog

  reply	other threads:[~2020-07-31  7:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-28 11:25 [PATCH] btrfs: handle errors from async submission Johannes Thumshirn
2020-07-29 14:01 ` Josef Bacik
2020-07-30 16:46 ` David Sterba
2020-07-31  7:39   ` Johannes Thumshirn [this message]
2020-07-31 14:12     ` David Sterba

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=SN4PR0401MB3598FF781B4DE1120955FCDC9B4E0@SN4PR0401MB3598.namprd04.prod.outlook.com \
    --to=johannes.thumshirn@wdc.com \
    --cc=dsterba@suse.cz \
    --cc=linux-btrfs@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 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 NNTP newsgroup(s).