From: Rusty Russell <rusty@ozlabs.org>
To: Greg KH <greg@kroah.com>, Alessandro Rubini <rubini@gnudd.com>
Cc: 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: Sat, 03 Dec 2011 15:21:43 +1030 [thread overview]
Message-ID: <87mxbaqmu8.fsf@rustcorp.com.au> (raw)
In-Reply-To: <20111202192701.GB13860@kroah.com>
On Fri, 2 Dec 2011 11:27:01 -0800, Greg KH <greg@kroah.com> wrote:
> On Fri, Dec 02, 2011 at 09:42:13AM +0100, Alessandro Rubini wrote:
> > > 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.
>
> Yes, that's what me and Linus have asked about having in the past,
> making things easier to merge and the like. Now admittedly, this file
> isn't all that hard to merge these days given that the addition of new
> busses is pretty rare, these complaints might have been from before git
> times, when merges were harder than they are now.
>
> Anyway, I like your patch as well, as it seems to get us to that goal.
But it doesn't :( Trivial conflict in file2alias.c becomes trivial
conflict in Makefile.
We could use $(wildcard) in the Makefile, but that's not used much in
the kernel so it'd seem a bit weird.
So honestly, I think we should reorder file2alias.c into alphabetical
order. In practice, that'll prevent conflicts.
As I said, I'm happy for Alessandro to do the separate file thing *too*,
but if that was the only point, there wasn't one.
Cheers,
Rusty.
prev parent reply other threads:[~2011-12-04 10:50 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
2011-12-02 19:27 ` Greg KH
2011-12-03 4:51 ` Rusty Russell [this message]
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=87mxbaqmu8.fsf@rustcorp.com.au \
--to=rusty@ozlabs.org \
--cc=dave.martin@linaro.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manohar.vanga@cern.ch \
--cc=rubini@gnudd.com \
--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