From: rubini@unipv.it (Alessandro Rubini)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: amba: Enable module alias autogeneration for AMBA drivers
Date: Tue, 22 Nov 2011 16:19:42 +0100 [thread overview]
Message-ID: <20111122151942.GA24821@mail.gnudd.com> (raw)
In-Reply-To: <20111122120756.GF2066@localhost.localdomain>
>> 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
next prev parent reply other threads:[~2011-11-22 15:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20111206151541.GA13774@linaro.org>
2011-11-22 11:32 ` [GIT PULL] ARM: amba: Enable module alias autogeneration for AMBA drivers Dave Martin
2011-11-22 11:56 ` Alessandro Rubini
2011-11-22 12:07 ` Dave Martin
2011-11-22 15:19 ` Alessandro Rubini [this message]
2011-11-22 19:20 ` Greg KH
2011-12-06 15:59 ` Alessandro Rubini
2011-12-06 16:18 ` Dave Martin
2011-12-19 13:24 ` Dave Martin
2011-12-19 21:39 ` Russell King - ARM Linux
2011-12-22 11:21 ` Dave Martin
2011-12-22 18:50 ` Russell King - ARM Linux
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20111122151942.GA24821@mail.gnudd.com \
--to=rubini@unipv.it \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).