linux-kernel - Re: [PATCH v3 00/44] Meta 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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20130112095507.GA1738@balrog>
Date:	Sat, 12 Jan 2013 09:55:07 +0000
From:	James Hogan <james.hogan@...tec.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org,
	Alexander Viro <viro@...iv.linux.org.uk>
Subject: Re: [PATCH v3 00/44] Meta Linux Kernel Port

Hi Stephen, Al,

On Sat, Jan 12, 2013 at 12:09:57PM +1100, Stephen Rothwell wrote:
> On Fri, 11 Jan 2013 15:02:06 +0000 James Hogan <james.hogan@...tec.com> wrote:
> >
> > Okay, I've rebased the metag tree from linux-next onto the master branch
> > of Al's signal tree (to get Vineet's GENERIC_SIGALTSTACK fix and
> > GENERIC_SIGALTSTACK's eventual removal).
> 
> OK, but I hope you mentioned not rebasing to Al.

I'm still rebasing the metag tree, and it's not quite ready for -next so
I don't mind if Al's tree rebases at this stage tbh.

Al: I don't know if you normally rebase your tree, but if it's okay with
you I'll let you know when I need it not to be rebased.

> > git://github.com/jahogan/metag-linux.git
> > branch: metag-core
> > tag: metag-core-v3.1
> 
> When you think it is sufficiently ready (and I am guessing that it is
> getting pretty close), please send me a request to add it to linux-next.

Thanks, will do.

Would "sufficiently ready" normally mean "in a state ready to send a
pull request to Linus"?

Thanks
James

Content of type "application/pgp-signature" skipped