linux-kernel - Re: linux-sh for-next reactivation

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20200603084105.47bd62c5@canb.auug.org.au>
Date:   Wed, 3 Jun 2020 08:41:05 +1000
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Rich Felker <dalias@...c.org>
Cc:     Linux Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux-sh list <linux-sh@...r.kernel.org>,
        Yoshinori Sato <ysato@...rs.sourceforge.jp>
Subject: Re: linux-sh for-next reactivation

Hi Rich,

On Tue, 2 Jun 2020 16:28:33 -0400 Rich Felker <dalias@...c.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@...c.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@...b.auug.org.au

Content of type "application/pgp-signature" skipped