From: Andrew Morton <akpm@linux-foundation.org>
To: Jean Delvare <khali@linux-fr.org>
Cc: benh@kernel.crashing.org, linux-fbdev-devel@lists.sourceforge.net
Subject: Re: [PATCH] radeonfb: Give i2c buses nicer names
Date: Thu, 31 Jul 2008 01:57:51 -0700 [thread overview]
Message-ID: <20080731015751.9d78e1af.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080608155056.4506f457@hyperion.delvare>
On Sun, 8 Jun 2008 15:50:56 +0200 Jean Delvare <khali@linux-fr.org> wrote:
> On Fri, 06 Jun 2008 19:21:37 +1000, Benjamin Herrenschmidt wrote:
> > On Fri, 2008-06-06 at 11:19 +0200, Jean Delvare wrote:
> > > The name of the i2c buses shows in the output of "i2cdetect -l", so
> > > it's important to give informative names.
> > >
> > > Signed-off-by: Jean Delvare <khali@linux-fr.org>
> >
> > Acked-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
>
> Hmm, does this mean that you won't take care of pushing the patch
> upstream? Driver maintainers usually do that...
Tony hasn't been heard from in many months and I only very occasionally
troll linux-fbdev-devel for lost things.
Is this patch still good? If so, in which of
2.6.25/2.6.26/2.6.27/2.6.28 do you think it should be merged?
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
next prev parent reply other threads:[~2008-07-31 8:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-06 9:19 [PATCH] radeonfb: Give i2c buses nicer names Jean Delvare
2008-06-06 9:21 ` Benjamin Herrenschmidt
2008-06-08 13:50 ` Jean Delvare
2008-07-31 8:57 ` Andrew Morton [this message]
2008-07-31 9:00 ` Benjamin Herrenschmidt
-- strict thread matches above, loose matches on Subject: below --
2008-06-17 12:46 Jean Delvare
2008-06-18 18:57 ` Krzysztof Helt
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=20080731015751.9d78e1af.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=khali@linux-fr.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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).