linux-kernel - linux-next: sh tree (Was:Re: [PATCH 07/11] sh: fix several build failures from system.h fallout)

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

Message-Id: <20120406164032.8fa7ddee4857f6e9cccdcf33@canb.auug.org.au>
Date:	Fri, 6 Apr 2012 16:40:32 +1000
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Paul Mundt <lethal@...ux-sh.org>
Cc:	Paul Gortmaker <paul.gortmaker@...driver.com>,
	linux-kernel@...r.kernel.org, linux-next@...r.kernel.org
Subject: linux-next: sh tree (Was:Re: [PATCH 07/11] sh: fix several build
 failures from system.h fallout)

Hi Paul,

On Fri, 6 Apr 2012 00:15:59 +0900 Paul Mundt <lethal@...ux-sh.org> wrote:
>
> On Wed, Apr 04, 2012 at 10:49:30PM -0400, Paul Gortmaker wrote:
> > 
> > Is this the tree Stephen should be using in linux-next?
> > 
> >         git://github.com/pmundt/linux-sh.git sh-latest
> 
> Yes, that's the current one for sh stuff for now. The rmobile stuff is
> going through the ARM SoC tree nowadays, so that shouldn't matter.  I
> haven't bothered getting the trees back on kernel.org yet, so I haven't
> updated the MAINTAINERS entry, but will probably do so in the future.

OK, I have added that back - using the sh-latest branch for the sh tree
and the sh-fixes-for-linus branch for sh-current (maybe the sh/urgent
branch would be better?).

-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au

Content of type "application/pgp-signature" skipped