From: Christoph Hellwig <hch@lst.de>
To: NeilBrown <neilb@suse.de>
Cc: Jens Axboe <axboe@fb.com>,
device-mapper development <dm-devel@redhat.com>,
"Kernel.org-Linux-RAID" <linux-raid@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@lst.de>,
stable@vger.kernel.org,
Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
Greg KH <gregkh@linuxfoundation.org>
Subject: Re: [PATCH v2 RESEND] block: discard bdi_unregister() in favour of bdi_destroy()
Date: Tue, 19 May 2015 08:21:36 +0200 [thread overview]
Message-ID: <20150519062136.GA29468@lst.de> (raw)
In-Reply-To: <20150519155837.456ad30e@notabene.brown>
Looks good,
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2015-05-19 6:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-19 5:58 [PATCH v2 RESEND] block: discard bdi_unregister() in favour of bdi_destroy() NeilBrown
2015-05-19 6:21 ` Christoph Hellwig [this message]
2015-05-19 9:40 ` Sergey Senozhatsky
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=20150519062136.GA29468@lst.de \
--to=hch@lst.de \
--cc=axboe@fb.com \
--cc=dm-devel@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=stable@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).