* linux-sh for-next reactivation
@ 2020-06-02 3:11 ` Rich Felker
0 siblings, 0 replies; 12+ messages in thread
From: Rich Felker @ 2020-06-02 3:11 UTC (permalink / raw)
To: Stephen Rothwell
Cc: Linux Next Mailing List, Linux Kernel Mailing List,
Linux-sh list, Yoshinori Sato
Stephen,
Could you reactivate linux-next pull from my arch/sh for-next branch?
It's where it was before, at:
git://git.libc.org/linux-sh for-next
and has newly accepted patches ready.
Rich
^ permalink raw reply [flat|nested] 12+ messages in thread* linux-sh for-next reactivation @ 2020-06-02 3:11 ` Rich Felker 0 siblings, 0 replies; 12+ messages in thread From: Rich Felker @ 2020-06-02 3:11 UTC (permalink / raw) To: Stephen Rothwell Cc: Linux Next Mailing List, Linux Kernel Mailing List, Linux-sh list, Yoshinori Sato Stephen, Could you reactivate linux-next pull from my arch/sh for-next branch? It's where it was before, at: git://git.libc.org/linux-sh for-next and has newly accepted patches ready. Rich ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: linux-sh for-next reactivation 2020-06-02 3:11 ` Rich Felker @ 2020-06-02 5:00 ` Stephen Rothwell -1 siblings, 0 replies; 12+ messages in thread From: Stephen Rothwell @ 2020-06-02 5:00 UTC (permalink / raw) To: Rich Felker Cc: Linux Next Mailing List, Linux Kernel Mailing List, Linux-sh list, Yoshinori Sato [-- Attachment #1: Type: text/plain, Size: 1151 bytes --] Hi Rich, On Mon, 1 Jun 2020 23:11:39 -0400 Rich Felker <dalias@libc.org> wrote: > > Could you reactivate linux-next pull from my arch/sh for-next branch? > It's where it was before, at: > > git://git.libc.org/linux-sh for-next > > and has newly accepted patches ready. I already have an SH tree from git://git.sourceforge.jp/gitroot/uclinux-h8/linux.git#sh-next . Should I do anything with that one? It currently contains: $ git log --oneline origin/master..sh/sh-next a193018e5290 (sh/sh-next) sh: add missing EXPORT_SYMBOL() for __delay 1d5fd6c33b04 sh: add missing DECLARE_EXPORT() for __ashiftrt_r4_xx d70f1e3d5dbd Merge remote-tracking branch 'origin/master' into sh-next baf58858e8b6 sh: prefer __section from compiler_attributes.h 8619b5a9035a sh: Drop -Werror from kernel Makefile 3a3a78124693 sh: kernel: disassemble: Mark expected switch fall-throughs fb8f77490f55 sh: kernel: hw_breakpoint: Fix missing break in switch statement cd10afbc932d sh: remove unneeded uapi asm-generic wrappers cbfc6edb6a4a sh: use __builtin_constant_p() directly instead of IS_IMMEDIATE() -- Cheers, Stephen Rothwell [-- Attachment #2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 488 bytes --] ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: linux-sh for-next reactivation @ 2020-06-02 5:00 ` Stephen Rothwell 0 siblings, 0 replies; 12+ messages in thread From: Stephen Rothwell @ 2020-06-02 5:00 UTC (permalink / raw) To: Rich Felker Cc: Linux Next Mailing List, Linux Kernel Mailing List, Linux-sh list, Yoshinori Sato [-- Attachment #1: Type: text/plain, Size: 1151 bytes --] Hi Rich, On Mon, 1 Jun 2020 23:11:39 -0400 Rich Felker <dalias@libc.org> wrote: > > Could you reactivate linux-next pull from my arch/sh for-next branch? > It's where it was before, at: > > git://git.libc.org/linux-sh for-next > > and has newly accepted patches ready. I already have an SH tree from git://git.sourceforge.jp/gitroot/uclinux-h8/linux.git#sh-next . Should I do anything with that one? It currently contains: $ git log --oneline origin/master..sh/sh-next a193018e5290 (sh/sh-next) sh: add missing EXPORT_SYMBOL() for __delay 1d5fd6c33b04 sh: add missing DECLARE_EXPORT() for __ashiftrt_r4_xx d70f1e3d5dbd Merge remote-tracking branch 'origin/master' into sh-next baf58858e8b6 sh: prefer __section from compiler_attributes.h 8619b5a9035a sh: Drop -Werror from kernel Makefile 3a3a78124693 sh: kernel: disassemble: Mark expected switch fall-throughs fb8f77490f55 sh: kernel: hw_breakpoint: Fix missing break in switch statement cd10afbc932d sh: remove unneeded uapi asm-generic wrappers cbfc6edb6a4a sh: use __builtin_constant_p() directly instead of IS_IMMEDIATE() -- Cheers, Stephen Rothwell [-- Attachment #2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 488 bytes --] ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: linux-sh for-next reactivation 2020-06-02 5:00 ` Stephen Rothwell @ 2020-06-02 20:28 ` Rich Felker -1 siblings, 0 replies; 12+ messages in thread From: Rich Felker @ 2020-06-02 20:28 UTC (permalink / raw) To: Stephen Rothwell Cc: Linux Next Mailing List, Linux Kernel Mailing List, Linux-sh list, Yoshinori Sato On Tue, Jun 02, 2020 at 03:00:39PM +1000, Stephen Rothwell wrote: > Hi Rich, > > On Mon, 1 Jun 2020 23:11:39 -0400 Rich Felker <dalias@libc.org> wrote: > > > > Could you reactivate linux-next pull from my arch/sh for-next branch? > > It's where it was before, at: > > > > git://git.libc.org/linux-sh for-next > > > > and has newly accepted patches ready. > > I already have an SH tree from > git://git.sourceforge.jp/gitroot/uclinux-h8/linux.git#sh-next . Should > I do anything with that one? > > It currently contains: > > $ git log --oneline origin/master..sh/sh-next > a193018e5290 (sh/sh-next) sh: add missing EXPORT_SYMBOL() for __delay > 1d5fd6c33b04 sh: add missing DECLARE_EXPORT() for __ashiftrt_r4_xx > d70f1e3d5dbd Merge remote-tracking branch 'origin/master' into sh-next > baf58858e8b6 sh: prefer __section from compiler_attributes.h > 8619b5a9035a sh: Drop -Werror from kernel Makefile > 3a3a78124693 sh: kernel: disassemble: Mark expected switch fall-throughs > fb8f77490f55 sh: kernel: hw_breakpoint: Fix missing break in switch statement > cd10afbc932d sh: remove unneeded uapi asm-generic wrappers > cbfc6edb6a4a sh: use __builtin_constant_p() directly instead of IS_IMMEDIATE() Hi Stephen, I completely forgot that you had the tree from our other co-maintainer Yoshinori Sato on the list linux-next is pulling from. Would it be okay to keep both? That would help with quickly identifying and resolving any conflicting commits and make things go more smoothly with two maintainers trying to be active. Let me know if this doesn't work for you and we'll figure out alternative arrangements. Rich ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: linux-sh for-next reactivation @ 2020-06-02 20:28 ` Rich Felker 0 siblings, 0 replies; 12+ messages in thread From: Rich Felker @ 2020-06-02 20:28 UTC (permalink / raw) To: Stephen Rothwell Cc: Linux Next Mailing List, Linux Kernel Mailing List, Linux-sh list, Yoshinori Sato On Tue, Jun 02, 2020 at 03:00:39PM +1000, Stephen Rothwell wrote: > Hi Rich, > > On Mon, 1 Jun 2020 23:11:39 -0400 Rich Felker <dalias@libc.org> wrote: > > > > Could you reactivate linux-next pull from my arch/sh for-next branch? > > It's where it was before, at: > > > > git://git.libc.org/linux-sh for-next > > > > and has newly accepted patches ready. > > I already have an SH tree from > git://git.sourceforge.jp/gitroot/uclinux-h8/linux.git#sh-next . Should > I do anything with that one? > > It currently contains: > > $ git log --oneline origin/master..sh/sh-next > a193018e5290 (sh/sh-next) sh: add missing EXPORT_SYMBOL() for __delay > 1d5fd6c33b04 sh: add missing DECLARE_EXPORT() for __ashiftrt_r4_xx > d70f1e3d5dbd Merge remote-tracking branch 'origin/master' into sh-next > baf58858e8b6 sh: prefer __section from compiler_attributes.h > 8619b5a9035a sh: Drop -Werror from kernel Makefile > 3a3a78124693 sh: kernel: disassemble: Mark expected switch fall-throughs > fb8f77490f55 sh: kernel: hw_breakpoint: Fix missing break in switch statement > cd10afbc932d sh: remove unneeded uapi asm-generic wrappers > cbfc6edb6a4a sh: use __builtin_constant_p() directly instead of IS_IMMEDIATE() Hi Stephen, I completely forgot that you had the tree from our other co-maintainer Yoshinori Sato on the list linux-next is pulling from. Would it be okay to keep both? That would help with quickly identifying and resolving any conflicting commits and make things go more smoothly with two maintainers trying to be active. Let me know if this doesn't work for you and we'll figure out alternative arrangements. Rich ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: linux-sh for-next reactivation 2020-06-02 20:28 ` Rich Felker @ 2020-06-02 22:41 ` Stephen Rothwell -1 siblings, 0 replies; 12+ messages in thread From: Stephen Rothwell @ 2020-06-02 22:41 UTC (permalink / raw) To: Rich Felker Cc: Linux Next Mailing List, Linux Kernel Mailing List, Linux-sh list, Yoshinori Sato [-- Attachment #1: Type: text/plain, Size: 2794 bytes --] Hi Rich, On Tue, 2 Jun 2020 16:28:33 -0400 Rich Felker <dalias@libc.org> wrote: > > On Tue, Jun 02, 2020 at 03:00:39PM +1000, Stephen Rothwell wrote: > > Hi Rich, > > > > On Mon, 1 Jun 2020 23:11:39 -0400 Rich Felker <dalias@libc.org> wrote: > > > > > > Could you reactivate linux-next pull from my arch/sh for-next branch? > > > It's where it was before, at: > > > > > > git://git.libc.org/linux-sh for-next > > > > > > and has newly accepted patches ready. > > > > I already have an SH tree from > > git://git.sourceforge.jp/gitroot/uclinux-h8/linux.git#sh-next . Should > > I do anything with that one? > > > > It currently contains: > > > > $ git log --oneline origin/master..sh/sh-next > > a193018e5290 (sh/sh-next) sh: add missing EXPORT_SYMBOL() for __delay > > 1d5fd6c33b04 sh: add missing DECLARE_EXPORT() for __ashiftrt_r4_xx > > d70f1e3d5dbd Merge remote-tracking branch 'origin/master' into sh-next > > baf58858e8b6 sh: prefer __section from compiler_attributes.h > > 8619b5a9035a sh: Drop -Werror from kernel Makefile > > 3a3a78124693 sh: kernel: disassemble: Mark expected switch fall-throughs > > fb8f77490f55 sh: kernel: hw_breakpoint: Fix missing break in switch statement > > cd10afbc932d sh: remove unneeded uapi asm-generic wrappers > > cbfc6edb6a4a sh: use __builtin_constant_p() directly instead of IS_IMMEDIATE() > > Hi Stephen, > > I completely forgot that you had the tree from our other co-maintainer > Yoshinori Sato on the list linux-next is pulling from. Would it be > okay to keep both? That would help with quickly identifying and > resolving any conflicting commits and make things go more smoothly > with two maintainers trying to be active. > > Let me know if this doesn't work for you and we'll figure out > alternative arrangements. Added from today (I called it "sh-rf" - if you want a different name, please let me know). 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] 12+ messages in thread
* Re: linux-sh for-next reactivation @ 2020-06-02 22:41 ` Stephen Rothwell 0 siblings, 0 replies; 12+ messages in thread From: Stephen Rothwell @ 2020-06-02 22:41 UTC (permalink / raw) To: Rich Felker Cc: Linux Next Mailing List, Linux Kernel Mailing List, Linux-sh list, Yoshinori Sato [-- Attachment #1: Type: text/plain, Size: 2794 bytes --] Hi Rich, On Tue, 2 Jun 2020 16:28:33 -0400 Rich Felker <dalias@libc.org> wrote: > > On Tue, Jun 02, 2020 at 03:00:39PM +1000, Stephen Rothwell wrote: > > Hi Rich, > > > > On Mon, 1 Jun 2020 23:11:39 -0400 Rich Felker <dalias@libc.org> wrote: > > > > > > Could you reactivate linux-next pull from my arch/sh for-next branch? > > > It's where it was before, at: > > > > > > git://git.libc.org/linux-sh for-next > > > > > > and has newly accepted patches ready. > > > > I already have an SH tree from > > git://git.sourceforge.jp/gitroot/uclinux-h8/linux.git#sh-next . Should > > I do anything with that one? > > > > It currently contains: > > > > $ git log --oneline origin/master..sh/sh-next > > a193018e5290 (sh/sh-next) sh: add missing EXPORT_SYMBOL() for __delay > > 1d5fd6c33b04 sh: add missing DECLARE_EXPORT() for __ashiftrt_r4_xx > > d70f1e3d5dbd Merge remote-tracking branch 'origin/master' into sh-next > > baf58858e8b6 sh: prefer __section from compiler_attributes.h > > 8619b5a9035a sh: Drop -Werror from kernel Makefile > > 3a3a78124693 sh: kernel: disassemble: Mark expected switch fall-throughs > > fb8f77490f55 sh: kernel: hw_breakpoint: Fix missing break in switch statement > > cd10afbc932d sh: remove unneeded uapi asm-generic wrappers > > cbfc6edb6a4a sh: use __builtin_constant_p() directly instead of IS_IMMEDIATE() > > Hi Stephen, > > I completely forgot that you had the tree from our other co-maintainer > Yoshinori Sato on the list linux-next is pulling from. Would it be > okay to keep both? That would help with quickly identifying and > resolving any conflicting commits and make things go more smoothly > with two maintainers trying to be active. > > Let me know if this doesn't work for you and we'll figure out > alternative arrangements. Added from today (I called it "sh-rf" - if you want a different name, please let me know). 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] 12+ messages in thread
* Re: linux-sh for-next reactivation 2020-06-02 22:41 ` Stephen Rothwell @ 2020-06-03 5:57 ` Yoshinori Sato -1 siblings, 0 replies; 12+ messages in thread From: Yoshinori Sato @ 2020-06-03 5:57 UTC (permalink / raw) To: Stephen Rothwell Cc: Rich Felker, Linux Next Mailing List, Linux Kernel Mailing List, Linux-sh list On Wed, 03 Jun 2020 07:41:05 +0900, Stephen Rothwell wrote: > > [1 <text/plain; US-ASCII (quoted-printable)>] > Hi Rich, > > On Tue, 2 Jun 2020 16:28:33 -0400 Rich Felker <dalias@libc.org> wrote: > > > > On Tue, Jun 02, 2020 at 03:00:39PM +1000, Stephen Rothwell wrote: > > > Hi Rich, > > > > > > On Mon, 1 Jun 2020 23:11:39 -0400 Rich Felker <dalias@libc.org> wrote: > > > > > > > > Could you reactivate linux-next pull from my arch/sh for-next branch? > > > > It's where it was before, at: > > > > > > > > git://git.libc.org/linux-sh for-next > > > > > > > > and has newly accepted patches ready. > > > > > > I already have an SH tree from > > > git://git.sourceforge.jp/gitroot/uclinux-h8/linux.git#sh-next . Should > > > I do anything with that one? > > > > > > It currently contains: > > > > > > $ git log --oneline origin/master..sh/sh-next > > > a193018e5290 (sh/sh-next) sh: add missing EXPORT_SYMBOL() for __delay > > > 1d5fd6c33b04 sh: add missing DECLARE_EXPORT() for __ashiftrt_r4_xx > > > d70f1e3d5dbd Merge remote-tracking branch 'origin/master' into sh-next > > > baf58858e8b6 sh: prefer __section from compiler_attributes.h > > > 8619b5a9035a sh: Drop -Werror from kernel Makefile > > > 3a3a78124693 sh: kernel: disassemble: Mark expected switch fall-throughs > > > fb8f77490f55 sh: kernel: hw_breakpoint: Fix missing break in switch statement > > > cd10afbc932d sh: remove unneeded uapi asm-generic wrappers > > > cbfc6edb6a4a sh: use __builtin_constant_p() directly instead of IS_IMMEDIATE() > > > > Hi Stephen, > > > > I completely forgot that you had the tree from our other co-maintainer > > Yoshinori Sato on the list linux-next is pulling from. Would it be > > okay to keep both? That would help with quickly identifying and > > resolving any conflicting commits and make things go more smoothly > > with two maintainers trying to be active. > > > > Let me know if this doesn't work for you and we'll figure out > > alternative arrangements. > > Added from today (I called it "sh-rf" - if you want a different name, > please let me know). > > 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 > [2 OpenPGP digital signature <application/pgp-signature (7bit)>] > No public key for 015042F34957D06C created at 2020-06-03T07:41:05+0900 using RSA I only provided it temporarily. Plase remove git://git.sourceforge.jp/gitroot/uclinux-h8/linux.git#sh-next Thanks. -- Yosinori Sato ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: linux-sh for-next reactivation @ 2020-06-03 5:57 ` Yoshinori Sato 0 siblings, 0 replies; 12+ messages in thread From: Yoshinori Sato @ 2020-06-03 5:57 UTC (permalink / raw) To: Stephen Rothwell Cc: Rich Felker, Linux Next Mailing List, Linux Kernel Mailing List, Linux-sh list On Wed, 03 Jun 2020 07:41:05 +0900, Stephen Rothwell wrote: > > [1 <text/plain; US-ASCII (quoted-printable)>] > Hi Rich, > > On Tue, 2 Jun 2020 16:28:33 -0400 Rich Felker <dalias@libc.org> wrote: > > > > On Tue, Jun 02, 2020 at 03:00:39PM +1000, Stephen Rothwell wrote: > > > Hi Rich, > > > > > > On Mon, 1 Jun 2020 23:11:39 -0400 Rich Felker <dalias@libc.org> wrote: > > > > > > > > Could you reactivate linux-next pull from my arch/sh for-next branch? > > > > It's where it was before, at: > > > > > > > > git://git.libc.org/linux-sh for-next > > > > > > > > and has newly accepted patches ready. > > > > > > I already have an SH tree from > > > git://git.sourceforge.jp/gitroot/uclinux-h8/linux.git#sh-next . Should > > > I do anything with that one? > > > > > > It currently contains: > > > > > > $ git log --oneline origin/master..sh/sh-next > > > a193018e5290 (sh/sh-next) sh: add missing EXPORT_SYMBOL() for __delay > > > 1d5fd6c33b04 sh: add missing DECLARE_EXPORT() for __ashiftrt_r4_xx > > > d70f1e3d5dbd Merge remote-tracking branch 'origin/master' into sh-next > > > baf58858e8b6 sh: prefer __section from compiler_attributes.h > > > 8619b5a9035a sh: Drop -Werror from kernel Makefile > > > 3a3a78124693 sh: kernel: disassemble: Mark expected switch fall-throughs > > > fb8f77490f55 sh: kernel: hw_breakpoint: Fix missing break in switch statement > > > cd10afbc932d sh: remove unneeded uapi asm-generic wrappers > > > cbfc6edb6a4a sh: use __builtin_constant_p() directly instead of IS_IMMEDIATE() > > > > Hi Stephen, > > > > I completely forgot that you had the tree from our other co-maintainer > > Yoshinori Sato on the list linux-next is pulling from. Would it be > > okay to keep both? That would help with quickly identifying and > > resolving any conflicting commits and make things go more smoothly > > with two maintainers trying to be active. > > > > Let me know if this doesn't work for you and we'll figure out > > alternative arrangements. > > Added from today (I called it "sh-rf" - if you want a different name, > please let me know). > > 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 > [2 OpenPGP digital signature <application/pgp-signature (7bit)>] > No public key for 015042F34957D06C created at 2020-06-03T07:41:05+0900 using RSA I only provided it temporarily. Plase remove git://git.sourceforge.jp/gitroot/uclinux-h8/linux.git#sh-next Thanks. -- Yosinori Sato ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: linux-sh for-next reactivation 2020-06-03 5:57 ` Yoshinori Sato @ 2020-06-03 12:52 ` Stephen Rothwell -1 siblings, 0 replies; 12+ messages in thread From: Stephen Rothwell @ 2020-06-03 12:52 UTC (permalink / raw) To: Yoshinori Sato Cc: Rich Felker, Linux Next Mailing List, Linux Kernel Mailing List, Linux-sh list [-- Attachment #1: Type: text/plain, Size: 312 bytes --] Hi Yoshinori, On Wed, 03 Jun 2020 14:57:32 +0900 Yoshinori Sato <ysato@users.sourceforge.jp> wrote: > > I only provided it temporarily. > Plase remove git://git.sourceforge.jp/gitroot/uclinux-h8/linux.git#sh-next OK, will do. I will also rename the sh-rf tree to sh. -- Cheers, Stephen Rothwell [-- Attachment #2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 488 bytes --] ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: linux-sh for-next reactivation @ 2020-06-03 12:52 ` Stephen Rothwell 0 siblings, 0 replies; 12+ messages in thread From: Stephen Rothwell @ 2020-06-03 12:52 UTC (permalink / raw) To: Yoshinori Sato Cc: Rich Felker, Linux Next Mailing List, Linux Kernel Mailing List, Linux-sh list [-- Attachment #1: Type: text/plain, Size: 312 bytes --] Hi Yoshinori, On Wed, 03 Jun 2020 14:57:32 +0900 Yoshinori Sato <ysato@users.sourceforge.jp> wrote: > > I only provided it temporarily. > Plase remove git://git.sourceforge.jp/gitroot/uclinux-h8/linux.git#sh-next OK, will do. I will also rename the sh-rf tree to sh. -- Cheers, Stephen Rothwell [-- Attachment #2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 488 bytes --] ^ permalink raw reply [flat|nested] 12+ messages in thread
end of thread, other threads:[~2020-06-03 12:52 UTC | newest] Thread overview: 12+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2020-06-02 3:11 linux-sh for-next reactivation Rich Felker 2020-06-02 3:11 ` Rich Felker 2020-06-02 5:00 ` Stephen Rothwell 2020-06-02 5:00 ` Stephen Rothwell 2020-06-02 20:28 ` Rich Felker 2020-06-02 20:28 ` Rich Felker 2020-06-02 22:41 ` Stephen Rothwell 2020-06-02 22:41 ` Stephen Rothwell 2020-06-03 5:57 ` Yoshinori Sato 2020-06-03 5:57 ` Yoshinori Sato 2020-06-03 12:52 ` Stephen Rothwell 2020-06-03 12:52 ` Stephen Rothwell
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.