From: Jens Axboe <axboe@suse.de>
To: "Adam J. Richter" <adam@yggdrasil.com>
Cc: thornber@sistina.com, linux-kernel@vger.kernel.org
Subject: Re: Patch(2.5.45): move io_restrictions to blkdev.h
Date: Sat, 2 Nov 2002 22:40:14 +0100 [thread overview]
Message-ID: <20021102214014.GF3612@suse.de> (raw)
In-Reply-To: <20021102105119.A6865@adam.yggdrasil.com>
On Sat, Nov 02 2002, Adam J. Richter wrote:
> This patch makes good on a threat that I posted yesterday
> to move struct io_restrictions from <linux/device-mapper.h> to
> <linux/blkdev.h>, eliminating duplication of a list of fields in
> struct request_queue.
Adam, I generally think the patch is a good idea. I also think it's a
very stupid time to start messing with stuff that is basically trivial
but still touches lost of stuff.
Please leave it alone for a few weeks.
> Jens, can I persuade you to integrate this change?
In due time, yes.
--
Jens Axboe
next prev parent reply other threads:[~2002-11-02 21:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-02 18:51 Patch(2.5.45): move io_restrictions to blkdev.h Adam J. Richter
2002-11-02 21:40 ` Jens Axboe [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-03 8:48 Adam J. Richter
2002-11-03 16:23 ` Joe Thornber
2002-11-03 22:03 Adam J. Richter
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=20021102214014.GF3612@suse.de \
--to=axboe@suse.de \
--cc=adam@yggdrasil.com \
--cc=linux-kernel@vger.kernel.org \
--cc=thornber@sistina.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