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: <57C28D85C66F5C49B9E212CBFAFDAC1F23013A86@CH1PRD0802MB115.namprd08.prod.outlook.com>
Date:	Wed, 29 Feb 2012 17:08:02 +0000
From:	Chris Kelly <ckelly@...odevices.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
CC:	Greg KH <gregkh@...uxfoundation.org>,
	"linux-next@...r.kernel.org" <linux-next@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: linux-next: build failure after merge of the final tree
 (staging tree related)

Hi Stephen,

Many thanks for your reply. This is exactly what I needed. I have submitted a patch to fix the problem and it builds OK with the compiler you suggested below.

Kind regards
Chris Kelly

-----Original Message-----
From: Stephen Rothwell [mailto:sfr@...b.auug.org.au] 
Sent: 29 February 2012 7:52 AM
To: Chris Kelly
Cc: Greg KH; linux-next@...r.kernel.org; linux-kernel@...r.kernel.org
Subject: Re: linux-next: build failure after merge of the final tree (staging tree related)

Hi Chris,

On Wed, 29 Feb 2012 07:35:35 +0000 Chris Kelly <ckelly@...odevices.com> wrote:
>
> Hi Greg,
> 
> I believe I understand the cause of the problem and would like to 
> submit a patch to fix it. However, I am unclear on what the starting 
> point is given that the final patch was reverted from linux-next. Do I 
> assume that patch will be reapplied before the applying the new patch 
> or should I provide another patch to reapply the reverted patch? Is it 
> acceptable to submit patches generated against the head of linux-next?

Your patches are all still in Greg's tree which I merge into linux-next every day.  I have then been reverting that last patch each day.  Your patch should be against Greg's tree (or your last patch) and then when the fix is in Greg's tree, I will get it in linux-next and stop reverting the other patch.

> Before submitting the patch, I would like to test that the patch 
> really does fix the issue found by Stephen. Since it doesn't occur 
> when building for x32 or x64 then I need to setup a PowerPC 
> cross-compile tool chain. Do you have any suggestions as to where I 
> can pull a prebuilt tool chain or do I need to build directly from the GNU sources.

http://www.kernel.org/pub/tools/crosstool/files/bin/x86_64/4.6.0/x86_64-gcc-4.6.0-nolibc_powerpc64-linux.tar.xz

That is am x86_64 hosted powerpc64 compiler suitable for building the kernel.

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

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ