From: Greg KH <greg@kroah.com>
To: Alessandro Rubini <rubini@gnudd.com>
Cc: rusty@ozlabs.org, 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 11:27:01 -0800 [thread overview]
Message-ID: <20111202192701.GB13860@kroah.com> (raw)
In-Reply-To: <20111202084213.GA3415@mail.gnudd.com>
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.
thanks,
greg k-h
next prev parent reply other threads:[~2011-12-02 19:31 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 [this message]
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=20111202192701.GB13860@kroah.com \
--to=greg@kroah.com \
--cc=dave.martin@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manohar.vanga@cern.ch \
--cc=rubini@gnudd.com \
--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