linux-kernel - Re: [PATCH v3 00/24] C6X: New architecture

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: <201109281633.05583.arnd@arndb.de>
Date:	Wed, 28 Sep 2011 16:33:05 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	Mark Salter <msalter@...hat.com>, linux-kernel@...r.kernel.org,
	linux-arch@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH v3 00/24] C6X: New architecture

On Wednesday 28 September 2011, Stephen Rothwell wrote:
>   Show Details
>   On Tue, 27 Sep 2011 16:29:41 -0400 Mark Salter <msalter@...hat.com> wrote:
> >
> > Here is v3 of the C6X architecture patch series. Patches are
> > available in 'upstream-v3' branch at:
> > 
> >     git@...ux-c6x.org:/git/projects/linux-c6x-upstreaming
> 
> Is it time for this to be included in linux-next (i.e. are you intending
> to send this to Linus during the next merge window)?  If so, please send
> a request (cc'd to here, linux-next and linux-kernel) asking for
> inclusion.  I would prefer a publically fetchable tree (the tree above is
> (implicitly) fetched over ssh and is so not generally available) and
> branch name that does not change over time (like "for-next" or something)
> but it can just be an alias for the above.
> 
> Arnd, do you have an opinion on this?

>From my perspective it can go into -next now. All the issues I have
reported in version 2 have been fixed, and the comments I made this
time are relatively insignificant, so I trust that Mark can fix those
either between now and the merge window or provide updates during the
3.2 bug fix phase. The only thing that absolutely needs to get fixed
before 3.2.0 IMO is the ptrace ABI since we can no longer change that
after a release, but it should also be a trivial change.

Thomas, you also had some important comments, please complain if you
see those as show-stoppers for integration into linux-next.

	Arnd
--
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/