LKML Archive on
help / color / mirror / Atom feed
From: Christoph Hellwig <>
To: "Leonid V. Fedorenchik" <>
Cc: Jonathan Corbet <>,
	Mike Christie <>,
	"Martin K. Petersen" <>,
	Jens Axboe <>, Hannes Reinecke <>,
	Jan Kara <>, Christoph Hellwig <>,,
Subject: Re: [PATCH] Documentation: Remove mentioning of block barriers
Date: Mon, 16 Mar 2015 13:26:17 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Fri, Mar 13, 2015 at 11:53:22PM +0300, Leonid V. Fedorenchik wrote:
> Remove mentioning of block barriers since they were removed.
> Signed-off-by: Leonid V. Fedorenchik <>

Looks good.

Reviewed-by: Christoph Hellwig <>

Re Jans comments:  this document is structurally out of date, as it's
framed aroudn the transition of the 2.4 to 2.5 block layer code.
Replacing it with something that just describes the current code
would be nice, nut not something I would want to bureden on someone
just removing the now incorrect parts of it.

And with blk-mq this is even more out of date now..

  parent reply	other threads:[~2015-03-16 12:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-13 20:53 Leonid V. Fedorenchik
2015-03-14  6:23 ` Jan Kara
2015-03-16 12:26 ` Christoph Hellwig [this message]
2015-03-19 20:57 ` Jonathan Corbet
2015-03-23 19:16   ` Leonid V. Fedorenchik

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \ \
    --subject='Re: [PATCH] Documentation: Remove mentioning of block barriers' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).