linux-kernel - Re: [PATCH v4 00/16] Cleanup Lemote FuLoong2e Support

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]

Message-ID: <20100617104735.GC24561@www.longlandclan.yi.org>
Date:	Thu, 17 Jun 2010 20:47:40 +1000
From:	Stuart Longland <redhatter@...too.org>
To:	Wu <wuzhangjin@...il.com>
Cc:	linux-kernel@...r.kernel.org, linux-mips@...ux-mips.org,
	ralf@...ux-mips.org, Yan Hua <yanh@...ote.com>,
	Philippe Vachon <philippe@...pig.ca>,
	Zhang Le <r0bertz@...too.org>,
	Zhang Fuxin <zhangfx@...ote.com>,
	loongson-dev <loongson-dev@...glegroups.com>,
	Liu Junliang <liujl@...ote.com>,
	Erwan Lerale <erwan@...scow.com>,
	Arnaud Patard <apatard@...driva.com>
Subject: Re: [PATCH v4 00/16] Cleanup Lemote FuLoong2e Support

Hi,
On Thu, Jul 02, 2009 at 11:15:52PM +0800, Wu wrote:
> From: Wu Zhangjin <wuzhangjin@...il.com>
>
> This patch series is the -v4 version of the loongson-PATCH-v3 series, but it
> only include the cleanup for fuloong2e support and necessary preparation for
> future fuloong-2f and yeeloong-2f support.
>
> The git branch of this patch series is:
>
> 	git://dev.lemote.com/rt4ls.git linux-loongson/dev/fuloong2e
>
> 	or
>
> 	http://dev.lemote.com/cgit/rt4ls.git/log/?h=linux-loongson/dev/fuloong2e

stuartl@...on ~/linux-fulong2e $ git fetch rt4ls
remote: Counting objects: 476834, done.
remote: Compressing objects: 100% (90281/90281), done.
remote: Total 452782 (delta 393459), reused 411290 (delta 359631)
Receiving objects: 100% (452782/452782), 152.90 MiB | 50 KiB/s, done.
Resolving deltas: 100% (393459/393459), completed with 15512 local
objects.
>From git://dev.lemote.com/rt4ls
 * [new branch]      linux-loongson/2.6.29/rt-preempt ->
 			rt4ls/linux-loongson/2.6.29/rt-preempt
 * [new branch]      linux-loongson/2.6.29/stable ->
			rt4ls/linux-loongson/2.6.29/stable
 * [new branch]      linux-loongson/2.6.30/stable ->
			rt4ls/linux-loongson/2.6.30/stable
 * [new branch]      linux-loongson/2.6.31/rt-preempt ->
			rt4ls/linux-loongson/2.6.31/rt-preempt
 * [new branch]      linux-loongson/2.6.31/stable ->
			rt4ls/linux-loongson/2.6.31/stable
 * [new branch]      linux-loongson/2.6.32/stable ->
			rt4ls/linux-loongson/2.6.32/stable
 * [new branch]      linux-loongson/2.6.33/stable ->
			rt4ls/linux-loongson/2.6.33/stable
 * [new branch]      linux-loongson/dev/2.6.30-gdium ->
			rt4ls/linux-loongson/dev/2.6.30-gdium
 * [new branch]      linux-loongson/dev/2.6.33-gdium ->
			rt4ls/linux-loongson/dev/2.6.33-gdium
 * [new branch]      linux-loongson/dev/kft ->
			rt4ls/linux-loongson/dev/kft
 * [new branch]      linux-loongson/dev/kgcov ->
			rt4ls/linux-loongson/dev/kgcov
 * [new branch]      master     -> rt4ls/master
 * [new branch]      rt/2.6.31/loongson -> rt4ls/rt/2.6.31/loongson
 * [new branch]      rt/2.6.31/mips -> rt4ls/rt/2.6.31/mips
 * [new branch]      rt/2.6.33/loongson -> rt4ls/rt/2.6.33/loongson
...

I can't seem to find a linux-loongson/dev/fuloong2e branch... did I miss
the boat?  I'm looking to update the kernels on the two Fulongs 2Es
here... as I'm having grief compiling Python 2.6 -- hard locks always at
the same point, and I have a feeling it's the
kernel+kernel-build-toolchain combo that's possibly to blame.

Regards,
--
Stuart Longland (aka Redhatter, VK4MSL)      .'''.
Gentoo Linux/MIPS Cobalt and Docs Developer  '.'` :
. . . . . . . . . . . . . . . . . . . . . .   .'.'
http://dev.gentoo.org/~redhatter             :.'

I haven't lost my mind...
  ...it's backed up on a tape somewhere.
--
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/