[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20170106081725.2aab4e1e@canb.auug.org.au>
Date: Fri, 6 Jan 2017 08:17:25 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Bartlomiej Zolnierkiewicz <b.zolnierkie@...sung.com>
Cc: linux-fbdev@...r.kernel.org, dri-devel@...ts.freedesktop.org,
linux-next@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: Please add fbdev-for-next to linux-next
Hi Bartlomiej,
On Thu, 05 Jan 2017 12:45:32 +0100 Bartlomiej Zolnierkiewicz <b.zolnierkie@...sung.com> wrote:
>
> Could you please add:
>
> git://github.com/bzolnier/linux.git fbdev-for-next
>
> To the linux-next tree?
>
> Linus has recently accepted u pull request from the fbdev-v4.10-rc2
> tag that added fbdev subsystem back into Maintained mode (with me as
> Maintainer).
Added from today.
Thanks for adding your subsystem tree as a participant of linux-next. As
you may know, this is not a judgement 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
Powered by blists - more mailing lists