From: Nicolas Ferre <nicolas.ferre@microchip.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>,
Ludovic Desroches <ludovic.desroches@microchip.com>,
ksummit-discuss@lists.linuxfoundation.org,
linux-kernel@vger.kernel.org
Subject: [Ksummit-discuss] at91 git tree in linux-next
Date: Wed, 22 Aug 2018 14:47:56 +0200 [thread overview]
Message-ID: <f15a82c8-5960-34ea-e7fc-dffdfdd369c6@microchip.com> (raw)
In-Reply-To: <551A9FAC.2010203@atmel.com>
Stephen,
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
Reference of previous request below... back in the days...
On 31/03/2015 at 15:22, Nicolas Ferre wrote:
> Hi Stephen,
>
> I am the maintainer for the Atmel ARM SoCs (aka at91) and I would like to
> know if it's possible for you to include my git tree in linux-next. It is
> usually pulled in by the ARM-soc guys (in copy).
>
> Here it is, with the branch that you would pull: "at91-next".
>
> git://git.kernel.org/pub/scm/linux/kernel/git/nferre/linux-at91.git at91-next
>
> I usually merge branches in this particular one when I send a pull-request to
> Arnd, Olof and Kevin so the material is usually pretty "stable".
>
> Thanks, bye,
>
--
Nicolas Ferre
next prev parent reply other threads:[~2018-08-22 12:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-31 13:22 at91 git tree in linux-next Nicolas Ferre
2015-03-31 13:22 ` Nicolas Ferre
2015-03-31 22:35 ` Stephen Rothwell
2015-03-31 22:35 ` Stephen Rothwell
2018-08-22 12:47 ` Nicolas Ferre [this message]
2018-08-22 23:30 ` [Ksummit-discuss] " Stephen Rothwell
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=f15a82c8-5960-34ea-e7fc-dffdfdd369c6@microchip.com \
--to=nicolas.ferre@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ludovic.desroches@microchip.com \
--cc=sfr@canb.auug.org.au \
/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.