From: Rich Felker <dalias@libc.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux-sh list <linux-sh@vger.kernel.org>,
Yoshinori Sato <ysato@users.sourceforge.jp>
Subject: Re: linux-sh for-next reactivation
Date: Tue, 02 Jun 2020 20:28:33 +0000 [thread overview]
Message-ID: <20200602202832.GA3776@brightrain.aerifal.cx> (raw)
In-Reply-To: <20200602150039.780a0ac0@canb.auug.org.au>
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
WARNING: multiple messages have this Message-ID (diff)
From: Rich Felker <dalias@libc.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux-sh list <linux-sh@vger.kernel.org>,
Yoshinori Sato <ysato@users.sourceforge.jp>
Subject: Re: linux-sh for-next reactivation
Date: Tue, 2 Jun 2020 16:28:33 -0400 [thread overview]
Message-ID: <20200602202832.GA3776@brightrain.aerifal.cx> (raw)
In-Reply-To: <20200602150039.780a0ac0@canb.auug.org.au>
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
next prev parent reply other threads:[~2020-06-02 20:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
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=20200602202832.GA3776@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=ysato@users.sourceforge.jp \
/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.