[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <cover.1322781825.git.rubini@gnudd.com>
Date: Fri, 2 Dec 2011 00:45:25 +0100
From: Alessandro Rubini <rubini@...dd.com>
To: linux-kernel@...r.kernel.org, greg@...ah.com, rusty@...abs.org
Cc: siglesia@...n.ch, manohar.vanga@...n.ch, dave.martin@...aro.org
Subject: [RFC PATCH V2 0/1] making order in file2alias
(this message is the RFC, the patch itself is expected to be fine)
This is a repost of what I've sent on Nov 4th. Since Rusty asked to
only do the first step, here it is. I rebased on next-20111201 and it
still works fine.
As for the previous 2/2 (see https://lkml.org/lkml/2011/11/4/127 ),
I still think it makes sense. And as Dave Martin suggested, we can
do without the array.
Thus, I may prepare three smaller steps, if that's acceptable (greg?)
step 1: create the ELF section so ENTRY() lines can leave the array
(and change name accordingly).
step 2: each ENTRY() line can be moved just after the associated code
(this means that a new bus is just a single hunk, not 2 of them)
step 3: I create the headers needed to move code and ENTRY in separate
files. This is some movement around, not trivial so it may
deserve a patch in itself.
step 4 and later ones: Individual busses may reach their own external file,
conditionally compiled per Kconfig rules.
If that's something worth evaluating, I can do that over the weekend.
thanks
/alessandro
Alessandro Rubini (1):
modpost: use table-lookup to build module aliases
scripts/mod/file2alias.c | 166 +++++++++++++++++-----------------------------
1 files changed, 60 insertions(+), 106 deletions(-)
--
1.7.7.2
--
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/
Powered by blists - more mailing lists