* [Ksummit-discuss] at91 git tree in linux-next [not found] <551A9FAC.2010203@atmel.com> @ 2018-08-22 12:47 ` Nicolas Ferre 2018-08-22 23:30 ` Stephen Rothwell 0 siblings, 1 reply; 4+ messages in thread From: Nicolas Ferre @ 2018-08-22 12:47 UTC (permalink / raw) To: Stephen Rothwell Cc: Alexandre Belloni, Ludovic Desroches, ksummit-discuss, linux-kernel 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 ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [Ksummit-discuss] at91 git tree in linux-next 2018-08-22 12:47 ` [Ksummit-discuss] at91 git tree in linux-next Nicolas Ferre @ 2018-08-22 23:30 ` Stephen Rothwell 2020-11-23 10:44 ` Geert Uytterhoeven 0 siblings, 1 reply; 4+ messages in thread From: Stephen Rothwell @ 2018-08-22 23:30 UTC (permalink / raw) To: Nicolas Ferre Cc: Alexandre Belloni, Ludovic Desroches, ksummit-discuss, linux-kernel [-- 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 --] ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [Ksummit-discuss] at91 git tree in linux-next 2018-08-22 23:30 ` Stephen Rothwell @ 2020-11-23 10:44 ` Geert Uytterhoeven 2020-11-23 11:59 ` Stephen Rothwell 0 siblings, 1 reply; 4+ messages in thread From: Geert Uytterhoeven @ 2020-11-23 10:44 UTC (permalink / raw) To: Stephen Rothwell; +Cc: Ludovic Desroches, ksummit, Linux Kernel Mailing List Hi Stephen, On Thu, Aug 23, 2018 at 1:31 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote: > 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. How is this working? From next-20201123: Merging at91/at91-next (0698efbb33ef Merge branches 'at91-soc', 'at91-dt' and 'at91-defconfig' into at91-next) which is indeed a recent commit, while Next/Trees has the wrong repo (linux-at91.git instead of linux.git): $ git show linux-next/master:Next/Trees | grep at91 at91-fixes git git://git.kernel.org/pub/scm/linux/kernel/git/at91/linux.git#at91-fixes at91 git git://git.kernel.org/pub/scm/linux/kernel/git/at91/linux-at91.git#at91-next $ git ls-remote git://git.kernel.org/pub/scm/linux/kernel/git/at91/linux-at91.git fatal: remote error: access denied or repository not exported: /pub/scm/linux/kernel/git/at91/linux-at91.git Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds _______________________________________________ Ksummit-discuss mailing list Ksummit-discuss@lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [Ksummit-discuss] at91 git tree in linux-next 2020-11-23 10:44 ` Geert Uytterhoeven @ 2020-11-23 11:59 ` Stephen Rothwell 0 siblings, 0 replies; 4+ messages in thread From: Stephen Rothwell @ 2020-11-23 11:59 UTC (permalink / raw) To: Geert Uytterhoeven; +Cc: Ludovic Desroches, ksummit, Linux Kernel Mailing List [-- Attachment #1.1: Type: text/plain, Size: 583 bytes --] Hi Geert, On Mon, 23 Nov 2020 11:44:17 +0100 Geert Uytterhoeven <geert@linux-m68k.org> wrote: > > How is this working? > > From next-20201123: > > Merging at91/at91-next (0698efbb33ef Merge branches 'at91-soc', > 'at91-dt' and 'at91-defconfig' into at91-next) > > which is indeed a recent commit, while Next/Trees has the wrong repo > (linux-at91.git instead of linux.git): That is what happens when you store the (supposedly) same information in 2 places :-( I have fixed the incorrect one. Thanks for letting me know. -- Cheers, Stephen Rothwell [-- Attachment #1.2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 488 bytes --] [-- Attachment #2: Type: text/plain, Size: 186 bytes --] _______________________________________________ Ksummit-discuss mailing list Ksummit-discuss@lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2020-11-23 11:59 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <551A9FAC.2010203@atmel.com>
2018-08-22 12:47 ` [Ksummit-discuss] at91 git tree in linux-next Nicolas Ferre
2018-08-22 23:30 ` Stephen Rothwell
2020-11-23 10:44 ` Geert Uytterhoeven
2020-11-23 11:59 ` Stephen Rothwell
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox