linux-kernel - Re: [PATCH v6 00/29] nios2 Linux kernel port

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] [day] [month] [year] [list]

Date:	Tue, 11 Nov 2014 11:00:05 +0800
From:	Ley Foon Tan <lftan@...era.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
CC:	Linux-Arch <linux-arch@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
	Arnd Bergmann <arnd@...db.de>,
	LeyFoon Tan <lftan.linux@...il.com>,
	Chung-Lin Tang <cltang@...esourcery.com>
Subject: Re: [PATCH v6 00/29] nios2 Linux kernel port

On Isn, 2014-11-10 at 00:12 +1100, Stephen Rothwell wrote:
> Hi,
> 
> On Fri, 7 Nov 2014 17:24:43 +0800 Ley Foon Tan <lftan@...era.com> wrote:
> >
> > On Fri, Nov 7, 2014 at 3:39 PM, LF.Tan <lftan.linux@...il.com> wrote:
> > >
> > > Review for Nios2 port is completed and ready for upstream. Can you
> > > please add nios2 patchset to linux-next?
> > >
> > > The following changes since commit 0df1f2487d2f0d04703f142813d53615d62a1da4:
> > >
> > >   Linux 3.18-rc3 (2014-11-02 15:01:51 -0800)
> > >
> > > are available in the git repository at:
> > >
> > >   http://git.rocketboards.org/linux-socfpga-next.git tags/nios2-for-linux-next
> > >
> > > for you to fetch changes up to 1b9e67a57ac633f407de11b36d8f996c368a8c66:
> > >
> > >   nios2: Build infrastructure (2014-11-06 15:23:37 +0800)
> >
> > By the way, I also created "nios2-next" branch for you to add to linux-next.
> > 
> > git://git.rocketboards.org/linux-socfpga-next.git nios2-next
> 
> Added from Monday with just you as the contact.
> 
> Thanks for adding your subsystem tree as a participant of linux-next.  As
> you may know, this is not a judgment 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.
Thanks. Saw it in linux-next.

Regards
Ley Foon



--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/