From: Jeff Garzik <jeff@garzik.org>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: axboe@kernel.dk, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] block: remove unused REQ_TYPE_LINUX_BLOCK
Date: Mon, 05 Jul 2010 14:43:22 -0400 [thread overview]
Message-ID: <4C3227CA.8000600@garzik.org> (raw)
In-Reply-To: <20100705181100B.fujita.tomonori@lab.ntt.co.jp>
On 07/05/2010 05:11 AM, FUJITA Tomonori wrote:
> You prefer to keep this for future possible users?
>
> This can be applied to block's for-2.6.36.
>
> =
> From: FUJITA Tomonori<fujita.tomonori@lab.ntt.co.jp>
> Subject: [PATCH] block: remove unused REQ_TYPE_LINUX_BLOCK
>
> Nobody uses REQ_TYPE_LINUX_BLOCK (and its REQ_LB_OP_*).
>
> Signed-off-by: FUJITA Tomonori<fujita.tomonori@lab.ntt.co.jp>
> ---
> include/linux/blkdev.h | 15 ---------------
> 1 files changed, 0 insertions(+), 15 deletions(-)
>
> diff --git a/include/linux/blkdev.h b/include/linux/blkdev.h
> index 3a2c5d9..baf5258 100644
> --- a/include/linux/blkdev.h
> +++ b/include/linux/blkdev.h
> @@ -60,7 +60,6 @@ enum rq_cmd_type_bits {
> REQ_TYPE_PM_RESUME, /* resume request */
> REQ_TYPE_PM_SHUTDOWN, /* shutdown request */
> REQ_TYPE_SPECIAL, /* driver defined type */
> - REQ_TYPE_LINUX_BLOCK, /* generic block layer message */
> /*
> * for ATA/ATAPI devices. this really doesn't belong here, ide should
> * use REQ_TYPE_SPECIAL and use rq->cmd[0] with the range of driver
> @@ -70,20 +69,6 @@ enum rq_cmd_type_bits {
> REQ_TYPE_ATA_PC,
> };
>
> -/*
> - * For request of type REQ_TYPE_LINUX_BLOCK, rq->cmd[0] is the opcode being
> - * sent down (similar to how REQ_TYPE_BLOCK_PC means that ->cmd[] holds a
> - * SCSI cdb.
> - *
> - * 0x00 -> 0x3f are driver private, to be used for whatever purpose they need,
> - * typically to differentiate REQ_TYPE_SPECIAL requests.
> - *
> - */
> -enum {
> - REQ_LB_OP_EJECT = 0x40, /* eject request */
> - REQ_LB_OP_FLUSH = 0x41, /* flush request */
> -};
Acked-by: Jeff Garzik <jgarzik@redhat.com>
Having a second level of opcodes, under REQ_TYPE_LINUX_BLOCK, always
seems less desirable than the current course of action you are now
pursuing (REQ_FLUSH, etc.)... nice cleanup.
Jeff
next prev parent reply other threads:[~2010-07-05 18:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-05 9:11 [PATCH] block: remove unused REQ_TYPE_LINUX_BLOCK FUJITA Tomonori
2010-07-05 11:17 ` Jens Axboe
2010-07-06 2:40 ` FUJITA Tomonori
2010-07-05 18:43 ` Jeff Garzik [this message]
2010-07-06 2:40 ` FUJITA Tomonori
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=4C3227CA.8000600@garzik.org \
--to=jeff@garzik.org \
--cc=axboe@kernel.dk \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.