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 for Android: free password hash cracker in your pocket

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

Date:	Wed, 28 Sep 2011 09:15:42 +1000
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Mark Salter <msalter@...hat.com>
Cc:	linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org,
	Arnd Bergmann <arnd@...db.de>
Subject: Re: [PATCH v3 00/24] C6X: New architecture

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?
-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au
http://www.canb.auug.org.au/~sfr/

Content of type "application/pgp-signature" skipped