linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: hch@lst.de, axboe@kernel.dk, martin.petersen@oracle.com,
	neilb@suse.de, bo.li.liu@oracle.com, linux-raid@vger.kernel.org,
	dm-devel@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] block: don't access bio->bi_error after bio_put()
Date: Tue, 11 Aug 2015 13:28:20 +0200	[thread overview]
Message-ID: <20150811112820.GA1493@lst.de> (raw)
In-Reply-To: <1439247918-12599-1-git-send-email-sasha.levin@oracle.com>

Hi Sasha,

thanks for the report.  I actually sent a similar patch to Jens
a couple days ago, but it seems he's on vacation currently asI haven't seen him
reply to this or other patches.

  reply	other threads:[~2015-08-11 11:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-10 23:05 [PATCH] block: don't access bio->bi_error after bio_put() Sasha Levin
2015-08-11 11:28 ` Christoph Hellwig [this message]
2015-08-11 17:32   ` Jens Axboe

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=20150811112820.GA1493@lst.de \
    --to=hch@lst.de \
    --cc=axboe@kernel.dk \
    --cc=bo.li.liu@oracle.com \
    --cc=dm-devel@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=neilb@suse.de \
    --cc=sasha.levin@oracle.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 NNTP newsgroup(s).