From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Jens Axboe <jens.axboe@oracle.com>,
FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] x86: replace BIO_VMERGE_BOUNDARY with BIOVEC_PHYS_MERGEABLE
Date: Thu, 30 Oct 2008 00:06:26 +1100 [thread overview]
Message-ID: <49085FD2.9090604@goop.org> (raw)
In-Reply-To: <20081029130338.GA26282@elte.hu>
Ingo Molnar wrote:
> uhm, 1/2 changes bio.h. I'll let both patches alone for now ;-)
OK, 1/2 should be applied one way or another. It's not critical, but it
avoids duplicating code if/when an arch/io.h wants to override
BIOVEC_PHYS_MERGEABLE.
J
next prev parent reply other threads:[~2008-10-29 13:07 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-24 5:41 [PATCH] x86: remove dead BIO_VMERGE_BOUNDARY definition FUJITA Tomonori
2008-10-24 20:58 ` Jeremy Fitzhardinge
2008-10-27 4:42 ` FUJITA Tomonori
2008-10-24 20:59 ` [PATCH 1/2] bio: define __BIOVEC_PHYS_MERGEABLE Jeremy Fitzhardinge
2008-10-24 20:59 ` [PATCH 2/2] x86: replace BIO_VMERGE_BOUNDARY with BIOVEC_PHYS_MERGEABLE Jeremy Fitzhardinge
2008-10-27 3:52 ` FUJITA Tomonori
2008-10-27 8:21 ` Jeremy Fitzhardinge
2008-10-27 8:37 ` FUJITA Tomonori
2008-10-27 9:18 ` Jeremy Fitzhardinge
2008-10-27 9:36 ` FUJITA Tomonori
2008-10-27 9:41 ` Jens Axboe
2008-10-27 11:43 ` Jeremy Fitzhardinge
2008-10-27 11:57 ` Jens Axboe
2008-10-28 23:06 ` FUJITA Tomonori
2008-10-29 8:37 ` Ingo Molnar
2008-10-29 9:24 ` Jeremy Fitzhardinge
2008-10-29 10:51 ` Ingo Molnar
2008-10-29 11:25 ` Ingo Molnar
2008-10-29 11:27 ` Jens Axboe
2008-10-29 11:30 ` Ingo Molnar
2008-10-29 11:34 ` Jens Axboe
2008-10-29 11:55 ` FUJITA Tomonori
2008-10-29 12:12 ` Jeremy Fitzhardinge
2008-10-29 13:03 ` Ingo Molnar
2008-10-29 13:06 ` Jeremy Fitzhardinge [this message]
2008-10-29 13:06 ` Jens Axboe
2008-10-29 9:27 ` 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=49085FD2.9090604@goop.org \
--to=jeremy@goop.org \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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.