linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alessandro Rubini <rubini@unipv.it>
To: dave.martin@linaro.org
Cc: linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, mmarek@suse.cz,
	greg@kroah.com, rusty@rustcorp.com.au
Subject: Re: [RFC PATCH 2/2] modpost: use config and ELF sections to build file2alias
Date: Wed, 23 Nov 2011 17:54:52 +0100	[thread overview]
Message-ID: <20111123165452.GA24139@mail.gnudd.com> (raw)
In-Reply-To: <20111123162842.GC2050@localhost.localdomain>

> I'm not the expert here, but I have a few comments that might be
> useful.

Yes, thanks.

> In files which define multiple bus types, there's no reason to put them
> all in the same array, so we can avoid the explicit boilerplate.

Nice catch, I'll do as you suggest.

> For myself, I have some misgivings about using this kind of toolchain
> trick where it is not needed -- though this is partly a matter of taste.
> 
> (To clarify, I think this stuff is only needed where the resulting
> [...]

This is needed because the bus abstraction and module autoloading
is so useful that we have a lot of uses, and they are ever increasing.
As said, in my current workgroup we have two new buses in the works.

> The problem to be solved here is essentially a source transofmration
> and should be possible to do straightforwardly with an autogenerated
> include file, a couple of Makefile rules and some scripting or
> preprocessor tricks to paste the relevant entries into a common
> array.

But the result is more hackish than this. ELF sections are well
understood and widely used in this environment, so the solution is
proved working. Scripting otherwise is an unneeded complication, as
every user will have to know a  new technique, which may break in
the future (e.g. gmake 3.82 broke some makefiles: each new trick is
a new risk).

> Otherwise, this series looks like a sensible evolution to me.

thanks
/alessandro

  reply	other threads:[~2011-11-23 16:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-04 12:23 [RGC PATCH 0/2] split file2alias using elf sections Alessandro Rubini
2011-11-04 12:23 ` [RFC PATCH 1/2] modpost: use table-lookup to build module aliases Alessandro Rubini
2011-11-04 12:23 ` [RFC PATCH 2/2] modpost: use config and ELF sections to build file2alias Alessandro Rubini
2011-11-23 16:28   ` Dave Martin
2011-11-23 16:54     ` Alessandro Rubini [this message]
2011-11-23 17:14       ` Dave Martin
2011-11-22 19:23 ` [RGC PATCH 0/2] split file2alias using elf sections Greg KH
2011-11-22 19:56   ` Alessandro Rubini
2011-11-30  5:09   ` Rusty Russell
2011-12-01  0:53     ` Alessandro Rubini

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=20111123165452.GA24139@mail.gnudd.com \
    --to=rubini@unipv.it \
    --cc=dave.martin@linaro.org \
    --cc=greg@kroah.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmarek@suse.cz \
    --cc=rusty@rustcorp.com.au \
    /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).