linux-kernel - Re: [RGC PATCH 0/2] split file2alias using elf sections

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20111122192300.GA5052@kroah.com>
Date:	Tue, 22 Nov 2011 11:23:00 -0800
From:	Greg KH <greg@...ah.com>
To:	Alessandro Rubini <rubini@...dd.com>
Cc:	linux-kernel@...r.kernel.org, siglesia@...n.ch,
	manohar.vanga@...n.ch
Subject: Re: [RGC PATCH 0/2] split file2alias using elf sections

On Fri, Nov 04, 2011 at 01:23:00PM +0100, Alessandro Rubini wrote:
> When adding a new bus type with autoloading of modules, people should
> always change the global scripts/mod/file2alias.c source file, whereas
> most of the new code is just new files and individual Makefile/Kconfig
> lines.
> 
> The first patch turns all the "normal" alias generation in a
> table-driven loop. The second patch moves a few alias types out of the
> main file2alias.c source, as a demonstration that the thing works.
> 
> I didn't move all bus/alias types out of the main file, as it's a huge
> work. But if the approach is going to be accepted I can do that (or
> happily leave the task to who volunteers).

Yes!!!!

I've been wanting this for years, and so have others (Linus, Andrew,
etc.)

I'll gladly take this through my driver-core tree, as it can handle
cross-bus issues like this.

Do you feel this series is good enough to accept, or do you want to
respin it again?

thanks,

greg k-h
--
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/