ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Nicolas Ferre <nicolas.ferre@microchip.com>
Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>,
	Ludovic Desroches <ludovic.desroches@microchip.com>,
	ksummit-discuss@lists.linuxfoundation.org,
	linux-kernel@vger.kernel.org
Subject: Re: [Ksummit-discuss] at91 git tree in linux-next
Date: Thu, 23 Aug 2018 09:30:45 +1000	[thread overview]
Message-ID: <20180823093045.00e751b0@canb.auug.org.au> (raw)
In-Reply-To: <f15a82c8-5960-34ea-e7fc-dffdfdd369c6@microchip.com>

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

Hi all,

On Wed, 22 Aug 2018 14:47:56 +0200 Nicolas Ferre <nicolas.ferre@microchip.com> wrote:
>
> Alexandre Ludovic and myself are the group of maintainers for Microchip 
> ARM SoCs. The current tree that we have in linux-next is mine [1] and we 
> are moving to a common group kernel.org tree.
> 
> So, can you please add our new tree to linux-next:
> at91 git 
> git://git.kernel.org/pub/scm/linux/kernel/git/at91/linux.git#at91-next
> 
> instead of:
> git://git.kernel.org/pub/scm/linux/kernel/git/nferre/linux-at91.git#at91-next
> 
> In addition to that, we also have now a "fixes" branch. Can you please 
> add it to your "fixes" tree?
> 
> at91 git 
> git://git.kernel.org/pub/scm/linux/kernel/git/at91/linux.git#at91-fixes
> 
> Thanks for your help, best regards,
>    Nicolas
> 
> 
> [1] 
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/Next/Trees#n84

All done.  I added Alexandre and Ludovic as contacts for both trees as
well.

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

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2018-08-22 23:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <551A9FAC.2010203@atmel.com>
2018-08-22 12:47 ` Nicolas Ferre
2018-08-22 23:30   ` Stephen Rothwell [this message]
2020-11-23 10:44     ` Geert Uytterhoeven
2020-11-23 11:59       ` Stephen Rothwell

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=20180823093045.00e751b0@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=alexandre.belloni@bootlin.com \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ludovic.desroches@microchip.com \
    --cc=nicolas.ferre@microchip.com \
    /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