From: Jens Axboe <axboe@suse.de>
To: Lou Langholtz <ldl@aros.net>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@digeo.com>
Subject: Re: [RFC][PATCH 2.6.0-test2] get rid of unused request_queue field queue_wait
Date: Mon, 28 Jul 2003 14:18:44 +0200 [thread overview]
Message-ID: <20030728121844.GE25356@suse.de> (raw)
In-Reply-To: <3F24D8B8.5030107@aros.net>
On Mon, Jul 28 2003, Lou Langholtz wrote:
> Are we going to use the queue_wait field of struct request_queue
> someday? As of 2.6.0-test2, I don't see any use of it. If it's not
> needed anymore, the following patch gets rid of it. Tested this patch by
> compiling for i386 and also doing a grep through all .h and .c files to
> see if it's used somewhere else (admittedly weak).
It's a relic from before dynamic request allocation, for now it can
definitely go.
--
Jens Axboe
next prev parent reply other threads:[~2003-07-28 12:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-28 8:03 [RFC][PATCH 2.6.0-test2] get rid of unused request_queue field queue_wait Lou Langholtz
2003-07-28 12:18 ` Jens Axboe [this message]
2003-07-28 13:20 ` 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=20030728121844.GE25356@suse.de \
--to=axboe@suse.de \
--cc=akpm@digeo.com \
--cc=ldl@aros.net \
--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 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).