linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Jarod Wilson <jarod@redhat.com>
Cc: linux-kernel@vger.kernel.org, Jens Axboe <axboe@fb.com>,
	Ming Lei <ming.lei@canonical.com>,
	Mike Galbraith <bitbucket@online.de>,
	Kent Overstreet <kmo@daterainc.com>,
	Mikulas Patocka <mpatocka@redhat.com>
Subject: Re: [PATCH] block/loop: improve reliability of partition scanning
Date: Wed, 1 Apr 2015 08:41:46 -0700	[thread overview]
Message-ID: <20150401154146.GA8596@infradead.org> (raw)
In-Reply-To: <1427834835-44412-1-git-send-email-jarod@redhat.com>

Please take a look at this thread and my suggestions in it:

https://lkml.org/lkml/2015/1/26/137
https://lkml.org/lkml/2015/1/26/564

  parent reply	other threads:[~2015-04-01 15:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-31 20:47 [PATCH] block/loop: improve reliability of partition scanning Jarod Wilson
2015-04-01 15:33 ` Ming Lei
2015-04-01 15:41 ` Christoph Hellwig [this message]
2015-04-01 23:30   ` Jarod Wilson

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=20150401154146.GA8596@infradead.org \
    --to=hch@infradead.org \
    --cc=axboe@fb.com \
    --cc=bitbucket@online.de \
    --cc=jarod@redhat.com \
    --cc=kmo@daterainc.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ming.lei@canonical.com \
    --cc=mpatocka@redhat.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).