From: Yoshinori Sato <ysato@users•sourceforge.jp>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Rich Felker <dalias@libc•org>,
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>
Subject: Re: linux-sh for-next reactivation
Date: Wed, 03 Jun 2020 14:57:32 +0900 [thread overview]
Message-ID: <87y2p4n12r.wl-ysato@users.sourceforge.jp> (raw)
In-Reply-To: <20200603084105.47bd62c5@canb.auug.org.au>
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
next prev parent reply other threads:[~2020-06-03 6:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-02 3:11 linux-sh for-next reactivation Rich Felker
2020-06-02 5:00 ` Stephen Rothwell
2020-06-02 20:28 ` Rich Felker
2020-06-02 22:41 ` Stephen Rothwell
2020-06-03 5:57 ` Yoshinori Sato [this message]
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=87y2p4n12r.wl-ysato@users.sourceforge.jp \
--to=ysato@users$(echo .)sourceforge.jp \
--cc=dalias@libc$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux-sh@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox