[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20150527072039.07aeea30@canb.auug.org.au>
Date: Wed, 27 May 2015 07:20:39 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Lee Jones <lee.jones@...aro.org>
Cc: Boris Brezillon <boris.brezillon@...e-electrons.com>,
linux-next@...r.kernel.org,
Nicolas Ferre <nicolas.ferre@...el.com>,
linux-arm-kernel@...ts.infradead.org, linux-pwm@...r.kernel.org,
thierry.reding@...il.com, jg1.han@...sung.com,
linux-kernel@...r.kernel.org,
Alexandre Belloni <alexandre.belloni@...e-electrons.com>
Subject: Re: [NEXT REQUEST][PATCH] backlight: pwm: handle EPROBE_DEFER while
requesting the PWM
Hi Lee,
On Tue, 26 May 2015 08:36:48 +0100 Lee Jones <lee.jones@...aro.org> wrote:
>
> It looks like my for-backlight-fixes branch isn't in -next.
>
> Stephen, could you rectify that please?
>
> M: git://git.kernel.org/pub/scm/linux/kernel/git/lee/backlight.git
Added from today.
Thanks for adding your subsystem tree as a participant of linux-next. As
you may know, this is not a judgment of your code. The purpose of
linux-next is for integration testing and to lower the impact of
conflicts between subsystems in the next merge window.
You will need to ensure that the patches/commits in your tree/series have
been:
* submitted under GPL v2 (or later) and include the Contributor's
Signed-off-by,
* posted to the relevant mailing list,
* reviewed by you (or another maintainer of your subsystem tree),
* successfully unit tested, and
* destined for the current or next Linux merge window.
Basically, this should be just what you would send to Linus (or ask him
to fetch). It is allowed to be rebased if you deem it necessary.
--
Cheers,
Stephen Rothwell
sfr@...b.auug.org.au
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists