From: Alessandro Rubini <rubini@gnudd.com>
To: rusty@ozlabs.org
Cc: greg@kroah.com, linux-kernel@vger.kernel.org, siglesia@cern.ch,
manohar.vanga@cern.ch, dave.martin@linaro.org
Subject: Re: [RFC PATCH V2 0/1] making order in file2alias
Date: Fri, 2 Dec 2011 09:42:13 +0100 [thread overview]
Message-ID: <20111202084213.GA3415@mail.gnudd.com> (raw)
In-Reply-To: <87pqg7r8q9.fsf@rustcorp.com.au>
> But splitting 15-line functions into separate files? Less compact, less
> simple.
Personally, I'm more interested in the addition of new busses (as
drop-in files) than the split up of current ones. But I see your point.
>> > 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.
> If you *really* want to use separate files, then this patch will let you
> do it. You'll need to expose some stuff in a header though.
Fine with me. This is 1 and 2 of my list above. And the "need to
expose" is my step 3. So I agree with this.
thanks
/alessandro
next prev parent reply other threads:[~2011-12-02 8:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-01 23:45 [RFC PATCH V2 0/1] making order in file2alias Alessandro Rubini
2011-12-01 23:45 ` [PATCH V2 1/1] modpost: use table-lookup to build module aliases Alessandro Rubini
2011-12-02 0:04 ` Greg KH
2011-12-02 0:03 ` [RFC PATCH V2 0/1] making order in file2alias Greg KH
2011-12-02 2:46 ` Rusty Russell
2011-12-02 8:42 ` Alessandro Rubini [this message]
2011-12-02 19:27 ` Greg KH
2011-12-03 4:51 ` Rusty Russell
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=20111202084213.GA3415@mail.gnudd.com \
--to=rubini@gnudd.com \
--cc=dave.martin@linaro.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manohar.vanga@cern.ch \
--cc=rusty@ozlabs.org \
--cc=siglesia@cern.ch \
/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