Re: [PATCH 2/2] x86: replace BIO_VMERGE_BOUNDARY with BIOVEC_PHYS_MERGEABLE

[Jens Axboe <jens.axboe@oracle.com>]

On Wed, Oct 29 2008, Ingo Molnar wrote:
> 
> * Jens Axboe <jens.axboe@oracle.com> wrote:
> 
> > 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?
> 
> the one i replied to (2/2), and which one Jeremy said was independent 
> of 1/2. Not so much it appears.

OK, those two are definitely connected, since the first one defines
__BIOVEC_PHYS_MERGEABLE :-)

The one I acked was in the mail I replied to, Tomos patch.

-- 
Jens Axboe