linux-kernel - Re: [PATCH 45/56] microblaze_v2: headers simple files

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, 6 May 2008 11:02:20 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	"Grant Likely" <grant.likely@...retlab.ca>
Cc:	"John Williams" <john.williams@...alogix.com>, monstr@...nam.cz,
	linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org,
	stephen.neuendorffer@...inx.com, John.Linn@...inx.com,
	matthew@....cx, will.newton@...il.com, drepper@...hat.com,
	microblaze-uclinux@...e.uq.edu.au,
	"Michal Simek" <monstr@...str.eu>
Subject: Re: [PATCH 45/56] microblaze_v2: headers simple files - empty or redirect to asm-generic

On Monday 05 May 2008, Grant Likely wrote:
> >  These are all just includes of asm-generic/* (hooray!).
> >
> >  But, is it reasonable to to suggest adding asm-generic at the end of the
> >  kernel include path, and save all this verbosity?
> >
> >  Principle of least surprise maybe?
> 
> Convention in the other archs is already established to explicitly
> include asm-generic files one by one.  It is probably best to match
> existing convention for commonality sake.

Right, I agree. We may eventually want to move to something more sophisticated,
but we should not change the current way of doing this while we're in the process
of adding a new architecture.

	Arnd <><
--
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/