All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Anatolij Gustschin <agust@denx.de>
Cc: linuxppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: Please pull 'next' branch of 5xxx tree
Date: Thu, 22 Mar 2012 01:08:31 +1100	[thread overview]
Message-ID: <20120322010831.3773462306b0f8a2753d2205@canb.auug.org.au> (raw)
In-Reply-To: <20120321011830.20e20ca0@wker>

[-- Attachment #1: Type: text/plain, Size: 1917 bytes --]

Hi Anatolij,

On Wed, 21 Mar 2012 01:18:30 +0100 Anatolij Gustschin <agust@denx.de> wrote:
>
> Yes. Stephen, could you please change linux-next to pull from my
> mpc5xxx tree
> 
>  git://git.denx.de/linux-2.6-agust.git next

I have replaced the 52xx-and-virtex tree with this (and called it simply
mpc5xxx).  I have also removed the 52xx-and-virtex-current tree.

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@canb.auug.org.au

Legal Stuff:
By participating in linux-next, your subsystem tree contributions are
public and will be included in the linux-next trees.  You may be sent
e-mail messages indicating errors or other issues when the
patches/commits from your subsystem tree are merged and tested in
linux-next.  These messages may also be cross-posted to the linux-next
mailing list, the linux-kernel mailing list, etc.  The linux-next tree
project and IBM (my employer) make no warranties regarding the linux-next
project, the testing procedures, the results, the e-mails, etc.  If you
don't agree to these ground rules, let me know and I'll remove your tree
from participation in linux-next.

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2012-03-21 14:08 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-20 17:04 Please pull 'next' branch of 5xxx tree Anatolij Gustschin
2012-03-20 22:30 ` Wolfram Sang
2012-03-20 23:32   ` Benjamin Herrenschmidt
2012-03-21  0:18     ` Anatolij Gustschin
2012-03-21 14:08       ` Stephen Rothwell [this message]
2012-03-21  0:56   ` Anatolij Gustschin
  -- strict thread matches above, loose matches on Subject: below --
2014-01-15 21:18 Anatolij Gustschin
2014-01-28  5:46 ` Anatolij Gustschin
2014-01-28  6:00   ` Benjamin Herrenschmidt
2014-01-28  6:22     ` Anatolij Gustschin
2014-01-29  7:46     ` Benjamin Herrenschmidt
2014-01-29 10:11       ` Gerhard Sittig
2014-01-29 20:50       ` Anatolij Gustschin
2013-11-04  0:11 Anatolij Gustschin
2013-09-03 20:39 Anatolij Gustschin
2013-09-05  6:50 ` Benjamin Herrenschmidt
2013-09-09  9:38   ` Anatolij Gustschin
2013-07-01 22:36 Anatolij Gustschin
2013-07-02  7:46 ` Benjamin Herrenschmidt
2013-07-02  8:00   ` Anatolij Gustschin
2013-07-02  8:29     ` Benjamin Herrenschmidt
2013-07-02 10:29     ` Benjamin Herrenschmidt
2013-07-02 10:35       ` Anatolij Gustschin
2013-04-29  9:42 Anatolij Gustschin
2013-02-19 23:57 Anatolij Gustschin
2012-12-11  8:23 Anatolij Gustschin
2012-09-24 14:45 Anatolij Gustschin
2011-09-30  6:31 Heiko Schocher
2011-09-30  6:38 ` Heiko Schocher
2011-09-29  9:30 Anatolij Gustschin
2011-09-29 12:49 ` Grant Likely
2011-09-22 23:20 Anatolij Gustschin
2011-09-23  0:15 ` Benjamin Herrenschmidt

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=20120322010831.3773462306b0f8a2753d2205@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=agust@denx.de \
    --cc=linuxppc-dev@ozlabs.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 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.