From: Jens Axboe <axboe@suse.de>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
Christoph Hellwig <hch@infradead.org>
Subject: Re: [RFC/PATCH] block: undeprecate ll_rw_block()
Date: Mon, 6 Feb 2006 22:07:05 +0100 [thread overview]
Message-ID: <20060206210705.GC5276@suse.de> (raw)
In-Reply-To: <1139254591.17774.5.camel@localhost>
On Mon, Feb 06 2006, Pekka Enberg wrote:
> From: Pekka Enberg <penberg@cs.helsinki.fi>
>
> This patch removes the DEPRECATED comment from ll_rw_block(). The function
> is still in active use and there isn't any real replacement for it.
It is still deprecated, so I think the comment should stay. There are
plenty ways to accomplish what ll_rw_block does (and more efficiently,
array of bh's is not very nice to say the least) and the buffer_head
isn't even an io unit anymore.
--
Jens Axboe
next prev parent reply other threads:[~2006-02-06 21:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-06 19:36 [RFC/PATCH] block: undeprecate ll_rw_block() Pekka Enberg
2006-02-06 21:07 ` Jens Axboe [this message]
2006-02-07 7:20 ` Pekka J Enberg
2006-02-07 7:41 ` 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=20060206210705.GC5276@suse.de \
--to=axboe@suse.de \
--cc=akpm@osdl.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
/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).