linux-kernel - Re: linux-next: build warning after merge of the moduleh tree

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]

Date:	Tue, 2 Aug 2011 18:35:58 +1000
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Jens Axboe <jaxboe@...ionio.com>
Cc:	Paul Gortmaker <paul.gortmaker@...driver.com>,
	"linux-next@...r.kernel.org" <linux-next@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Mike Christie <michaelc@...wisc.edu>
Subject: Re: linux-next: build warning after merge of the moduleh tree

Hi Jens,

On Tue, 2 Aug 2011 09:26:14 +0200 Jens Axboe <jaxboe@...ionio.com> wrote:
>
> Thanks, will you carry this until things are merged? Not easy for me to
> fix up.

Yes, no problem.  It is possible that the module.h split may not even go
into v3.1, in which case the fix patch will jst become part of the moduleh
tree after the block tree is merged.

Though the feedback to the original patch writer is that they should have
included module.h instead of relying on it being implicitly included.

You could include a patch to add an include of module.h to this file in
your tree - that way even if the module.h split goes ahead, your tree
won't get broken.  It could then be changed to the lighter weight
export.h later.
-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au
http://www.canb.auug.org.au/~sfr/

Content of type "application/pgp-signature" skipped