linux-kernel - Re: [PATCH 2/2] x86: replace BIO_VMERGE_BOUNDARY with BIOVEC_PHYS

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20081029113016.GA3751@elte.hu>
Date:	Wed, 29 Oct 2008 12:30:16 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Jens Axboe <jens.axboe@...cle.com>
Cc:	Jeremy Fitzhardinge <jeremy@...p.org>,
	FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] x86: replace BIO_VMERGE_BOUNDARY with
	BIOVEC_PHYS_MERGEABLE


* Jens Axboe <jens.axboe@...cle.com> wrote:

> On Wed, Oct 29 2008, Ingo Molnar wrote:
> > 
> > * Ingo Molnar <mingo@...e.hu> wrote:
> > 
> > > 
> > > * Jeremy Fitzhardinge <jeremy@...p.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.

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/