linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
	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: Wed, 29 Oct 2008 12:27:46 +0100	[thread overview]
Message-ID: <20081029112745.GT22217@kernel.dk> (raw)
In-Reply-To: <20081029112504.GA1935@elte.hu>

On Wed, Oct 29 2008, Ingo Molnar wrote:
> 
> * Ingo Molnar <mingo@elte.hu> wrote:
> 
> > 
> > * Jeremy Fitzhardinge <jeremy@goop.org> wrote:
> > 
> > >> does it have any dependency on:
> > >>
> > >>   Subject: [PATCH 1/2] bio: define __BIOVEC_PHYS_MERGEABLE
> > >
> > > No, they're independent.  Defining __BIOVEC_PHYS_MERGEABLE will be 
> > > useful for the Xen changes I need to make in the wake of Tomo's 
> > > patch.
> > 
> > ok - applied to tip/x86/xen, thanks Jeremy! (also added Jens's 
> > Acked-by)
> 
> build failure, zapped it:
> 
> fs/bio.c: In function '__bio_add_page':
> fs/bio.c:443: error: implicit declaration of function '__BIOVEC_PHYS_MERGEABLE'

What patch(es) did you apply?

-- 
Jens Axboe


  reply	other threads:[~2008-10-29 11:29 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 [this message]
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
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=20081029112745.GT22217@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=jeremy@goop.org \
    --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 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).