linux-kernel - Re: [GIT PULL] ARM: amba: Enable module alias autogeneration for AMBA drivers

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: <20111122151942.GA24821@mail.gnudd.com>
Date:	Tue, 22 Nov 2011 16:19:42 +0100
From:	Alessandro Rubini <rubini@...pv.it>
To:	dave.martin@...aro.org
Cc:	linux@....linux.org.uk, patches@...aro.org,
	linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
	alan@...ux.intel.com, a.zummo@...ertech.it,
	alsa-devel@...a-project.org, cjb@...top.org,
	dan.j.williams@...el.com, dmitry.torokhov@...il.com,
	grant.likely@...retlab.ca, perex@...ex.cz,
	jassisinghbrar@...il.com, julia@...u.dk, linus.walleij@...aro.org,
	linux-fbdev@...r.kernel.org, linux-input@...r.kernel.org,
	linux-mmc@...r.kernel.org, linux-serial@...r.kernel.org,
	linux-watchdog@...r.kernel.org, lethal@...ux-sh.org,
	Pawel.Moll@....com, rtc-linux@...glegroups.com,
	spi-devel-general@...ts.sourceforge.net, tiwai@...e.de,
	vinod.koul@...el.com, wim@...ana.be
Subject: Re: [GIT PULL] ARM: amba: Enable module alias autogeneration for
 AMBA drivers

>>   lkml.org/lkml/2011/11/4/125 (0/2: description of the work)
>>   lkml.org/lkml/2011/11/4/126 (1/2: turn the if plethora to table lookup)
>>   lkml.org/lkml/2011/11/4/127 (2/2: partial split to type-specific files).
> 
> Splitting this up doesn't look like a silly idea -- I thought it was
> unfortunate to have to patch a core file just to add a bus type.
>
> I guess the question is how many new buses we get over time.

Well, CERN will have 2 in a short time. And I'm sure the bus concept
is so good that a number of them exists as external patches. Being
forced to patch a core file is not good, with conflicts that accumulate
over time.

I'd better be able to drop in my own file and add a kconfig-aware line
in Makefile.  I think the implementation is straightforward. Who should
I send it to?

thanks
/alessandro
--
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/