All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@rpsys.net>
To: Len Brown <lenb@kernel.org>
Cc: linux-acpi@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	akpm <akpm@linux-foundation.org>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	jsimmons@infradead.org, linux-kernel@hansmi.ch,
	openembedded@hrw.one.pl,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: Re: git backlight tree
Date: Mon, 12 Feb 2007 13:43:27 +0000	[thread overview]
Message-ID: <1171287807.5898.122.camel@localhost.localdomain> (raw)
In-Reply-To: <200702102345.39855.lenb@kernel.org>

On Sat, 2007-02-10 at 23:45 -0500, Len Brown wrote:
> On Saturday 10 February 2007 19:33, Richard Purdie wrote:
> > As mentioned previously, I've setup a backlight git tree at:
> > 
> > http://git.o-hand.com/?p=linux-rpurdie-backlight;a=shortlog;h=for-mm
> > (git://git.o-hand.com/linux-rpurdie-backlight)
> > 
> > A patch of the combined changes to mainline is:
> > 
> > http://www.rpsys.net/openzaurus/patches/git_backlight-r1.patch.gz
> 
> The changes under drivers/acpi/ and drivers/misc/ look fine to me.
> Acked-by: Len Brown <len.brown@intel.com>
> if you need that to send those bits upstream.
> 
> Note that there is a new sony-laptop driver under drivers/misc/ in my tree
> that I expect to send upstream next week -- and it will need
> the analogous updates.

I'd noticed it and had sent Andrew a patch to keep things happy in -mm.
Now I know the timescales, I'll wait until after its gone in and fixup
the backlight tree accordingly before submitting.

Thanks,

Richard


      reply	other threads:[~2007-02-12 13:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-11  0:33 git backlight tree Richard Purdie
2007-02-11  4:45 ` Len Brown
2007-02-12 13:43   ` Richard Purdie [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=1171287807.5898.122.camel@localhost.localdomain \
    --to=rpurdie@rpsys.net \
    --cc=akpm@linux-foundation.org \
    --cc=benh@kernel.crashing.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=jsimmons@infradead.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@hansmi.ch \
    --cc=linux-kernel@vger.kernel.org \
    --cc=openembedded@hrw.one.pl \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.