linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Cc: linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Please add fbdev-for-next to linux-next
Date: Fri, 6 Jan 2017 08:17:25 +1100	[thread overview]
Message-ID: <20170106081725.2aab4e1e@canb.auug.org.au> (raw)
In-Reply-To: <3374870.z5x5pT8vjP@amdc3058>

Hi Bartlomiej,

On Thu, 05 Jan 2017 12:45:32 +0100 Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.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@canb.auug.org.au

      reply	other threads:[~2017-01-05 21:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20170105114535epcas5p38b89f23a8fbfdc198f703eb226153961@epcas5p3.samsung.com>
2017-01-05 11:45 ` Please add fbdev-for-next to linux-next Bartlomiej Zolnierkiewicz
2017-01-05 21:17   ` Stephen Rothwell [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=20170106081725.2aab4e1e@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=b.zolnierkie@samsung.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    /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).