linux-kernel - Re: linux-next: Tree for July 26 (uml)

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:	Tue, 14 Aug 2012 09:43:38 +0930
From:	Rusty Russell <rusty@...tcorp.com.au>
To:	Randy Dunlap <rdunlap@...otime.net>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	Richard Weinberger <richard@....at>,
	user-mode-linux-devel@...ts.sourceforge.net,
	"David Howells" <dhowells@...hat.com>
Subject: Re: linux-next: Tree for July 26 (uml)

On Mon, 13 Aug 2012 10:00:16 -0700, Randy Dunlap <rdunlap@...otime.net> wrote:
> On 07/26/2012 08:18 AM, Randy Dunlap wrote:
> 
> > On 07/25/2012 10:04 PM, Stephen Rothwell wrote:
> > 
> >> Hi all,
> >>
> >> Please do not add anything to linux-next included branches/series that is
> >> destined for v3.7 until after v3.6-rc1 is released.
> >>
> >> Reminder: do not rebase your branches before asking Linus to pull them ...
> >>
> >> Changes since 20120725:
> >>
> > 
> > 
> > 
> > uml on x86_64 (defconfig) build fails with:
> > 
> >   CC      arch/x86/um/../kernel/module.o
> > arch/x86/um/../kernel/module.c:96:5: error: redefinition of 'apply_relocate_add'
> > include/linux/moduleloader.h:64:19: note: previous definition of 'apply_relocate_add' was here
> > make[2]: *** [arch/x86/um/../kernel/module.o] Error 1
> > 
> > 
> > 
> 
> 
> 
> Adding Rusty.
> 
> 
> This build error is still happening for uml on x86_64
> in linux-next 20120813.

No huge surprise, I'll punt this to David Howells :)

Cheers,
Rusty.
--
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/