at91 git tree in linux-next
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,
Signature · 1 line
Nicolas Ferre
Hi Nicolas,
Quoted 11 lines · On Tue, 31 Mar 2015 15:22:52 +0200 Nicolas Ferre <[email protected]>…
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.gitat91-nextI 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".
Added from today.
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.
Signature · 10 lines
Cheers, Stephen Rothwell sfr at canb.auug.org.au -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150401/cbac310f/attachment.sig>
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...
Quoted 15 lines · Nicolas Ferre
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.gitat91-nextI 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,
Signature · 1 line
Nicolas Ferre
Hi all,
Quoted 18 lines · On Wed, 22 Aug 2018 14:47:56 +0200 Nicolas Ferre <[email protected]>…
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 gitgit://git.kernel.org/pub/scm/linux/kernel/git/at91/linux.git#at91-nextinstead of:
git://git.kernel.org/pub/scm/linux/kernel/git/nferre/linux-at91.git#at91-nextIn 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
Quoted 6 lines
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.
Signature · 3 lines
Cheers, Stephen Rothwell [email protected]
Hi Stephen,
Quoted 22 lines · Stephen Rothwell
Quoted 21 lines · On Wed, 22 Aug 2018 14:47:56 +0200 Nicolas Ferre <[email protected]>…
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 gitgit://git.kernel.org/pub/scm/linux/kernel/git/at91/linux.git#at91-nextinstead of:
git://git.kernel.org/pub/scm/linux/kernel/git/nferre/linux-at91.git#at91-nextIn 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-fixesThanks for your help, best regards,
Nicolas
Quoted 5 lines
Quoted 2 lines
[1]
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/Next/Trees#n84All 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 -- [email protected]
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 [email protected]
https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss
Hi Geert,
Quoted 10 lines · On Mon, 23 Nov 2020 11:44:17 +0100 Geert Uytterhoeven <[email protected]>…
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.
Signature · 2 lines
Cheers, Stephen Rothwell
_______________________________________________
Ksummit-discuss mailing list
[email protected]
https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss