linux-kernel - Re: [ALPHA] 2.6.28-rc fails to compile

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:	Wed, 29 Oct 2008 06:59:35 -0700
From:	Arjan van de Ven <arjan@...radead.org>
To:	Adrian Bunk <bunk@...nel.org>
Cc:	Raúl Porcel <armin76@...too.org>,
	linux-kernel@...r.kernel.org, linux-alpha@...r.kernel.org,
	Ivan Kokshaysky <ink@...assic.park.msu.ru>,
	klausman@...too.org, Jesse Barnes <jbarnes@...tuousgeek.org>,
	Andrew Morton <akpm@...ux-foundation.org>, rth@...ddle.net
Subject: Re: [ALPHA] 2.6.28-rc fails to compile

On Wed, 29 Oct 2008 15:45:53 +0200
Adrian Bunk <bunk@...nel.org> wrote:

> On Wed, Oct 29, 2008 at 06:27:41AM -0700, Arjan van de Ven wrote:
> > 
> > Andrew has a patch for this in his tree for a while... I was
> > assuming he'd do a patchdump to Linus late in -rc1 but it seems not
> > to have happened..
> 
> The basic problem for the Alpha build errors are circular #include's 
> (that are anyway a pretty bad thing), and I'm currently attacking
> that problem (it seems to be surprisingly easy).
> 
> That's IMHO better than the patch in -mm that uninlines 
> pci_ioremap_bar().

and in my opinion the uninline is nicer ;)
Because that means we can add more checks to it over time without
bloating the kernel.


-- 
Arjan van de Ven 	Intel Open Source Technology Centre
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org
--
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/