From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.8 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING,SPF_HELO_NONE,SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 923BBC433E1 for ; Wed, 3 Jun 2020 06:04:51 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 7BD10205CB for ; Wed, 3 Jun 2020 06:04:51 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725943AbgFCGEu (ORCPT ); Wed, 3 Jun 2020 02:04:50 -0400 Received: from mail02.asahi-net.or.jp ([202.224.55.14]:41832 "EHLO mail02.asahi-net.or.jp" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725792AbgFCGEt (ORCPT ); Wed, 3 Jun 2020 02:04:49 -0400 X-Greylist: delayed 432 seconds by postgrey-1.27 at vger.kernel.org; Wed, 03 Jun 2020 02:04:47 EDT Received: from sakura.ysato.name (ik1-413-38519.vs.sakura.ne.jp [153.127.30.23]) (Authenticated sender: PQ4Y-STU) by mail02.asahi-net.or.jp (Postfix) with ESMTPA id DEA73EE429; Wed, 3 Jun 2020 14:57:33 +0900 (JST) Received: from yo-satoh-debian.ysato.ml (z215094.dynamic.ppp.asahi-net.or.jp [110.4.215.94]) by sakura.ysato.name (Postfix) with ESMTPSA id 182B31C06C6; Wed, 3 Jun 2020 14:57:33 +0900 (JST) Date: Wed, 03 Jun 2020 14:57:32 +0900 Message-ID: <87y2p4n12r.wl-ysato@users.sourceforge.jp> From: Yoshinori Sato To: Stephen Rothwell Cc: Rich Felker , Linux Next Mailing List , Linux Kernel Mailing List , Linux-sh list Subject: Re: linux-sh for-next reactivation In-Reply-To: <20200603084105.47bd62c5@canb.auug.org.au> References: <20200602031123.GA1079@brightrain.aerifal.cx> <20200602150039.780a0ac0@canb.auug.org.au> <20200602202832.GA3776@brightrain.aerifal.cx> <20200603084105.47bd62c5@canb.auug.org.au> User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI-EPG/1.14.7 (Harue) FLIM/1.14.9 (=?ISO-8859-4?Q?Goj=F2?=) APEL/10.8 EasyPG/1.0.0 Emacs/26 (x86_64-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 03 Jun 2020 07:41:05 +0900, Stephen Rothwell wrote: > > [1 ] > Hi Rich, > > On Tue, 2 Jun 2020 16:28:33 -0400 Rich Felker 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 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 ] > 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