linux-kernel - Re: 2.6.29 -mm merge plans

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]

Date:	Mon, 5 Jan 2009 10:39:31 +0100
From:	Sam Ravnborg <sam@...nborg.org>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	David Miller <davem@...emloft.net>, akpm@...ux-foundation.org,
	linux-kernel@...r.kernel.org
Subject: Re: 2.6.29 -mm merge plans

On Mon, Jan 05, 2009 at 10:21:10AM +0100, Ingo Molnar wrote:
> 
> * David Miller <davem@...emloft.net> wrote:
> 
> > From: Andrew Morton <akpm@...ux-foundation.org>
> > Date: Mon, 5 Jan 2009 01:12:02 -0800
> > 
> > > On Mon, 5 Jan 2009 10:02:39 +0100 Sam Ravnborg <sam@...nborg.org> wrote:
> > > 
> > > > Hi Andrew.
> > > > 
> > > > > sparc64-use-unsigned-long-long-for-u64.patch
> > > > > sparc64-fix-unsigned-long-long-warnings-in-drivers.patch
> > > > 
> > > > Please drop these two.
> > > 
> > > Might, if they break my build.
> > 
> > They don't build, I tested them when I tried integrated Sam's patches.
> 
> do they break due to some warnings caught by -Werror?

Yup.
In my setup I did not see the warnings.
Most likely because I'm sitting on an older i386 and the
64 bit version of gcc emits more warnings than my 32 bit version.

The build broke in with Dave's native gcc and will most likely with
a 64 bit cross compiler too.

I do not want to remove the -Werror just due to this as it
is only a limited effort to fix up the patches when I get
my setup fixed.

But due to other issues (you know work and such) it it not the next week
that I have a proper setup.

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