From: Rusty Russell <rusty@rustcorp.com.au>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Richard Weinberger <richard@nod.at>,
user-mode-linux-devel@lists.sourceforge.net,
David Howells <dhowells@redhat.com>
Subject: Re: linux-next: Tree for July 26 (uml)
Date: Tue, 14 Aug 2012 09:43:38 +0930 [thread overview]
Message-ID: <87a9xys53h.fsf@rustcorp.com.au> (raw)
In-Reply-To: <502932A0.3060001@xenotime.net>
On Mon, 13 Aug 2012 10:00:16 -0700, Randy Dunlap <rdunlap@xenotime.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.
next prev parent reply other threads:[~2012-08-14 0:23 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-26 5:04 linux-next: Tree for July 26 Stephen Rothwell
2012-07-26 15:18 ` linux-next: Tree for July 26 (uml) Randy Dunlap
2012-08-13 17:00 ` Randy Dunlap
2012-08-14 0:13 ` Rusty Russell [this message]
2012-08-14 14:26 ` David Howells
2012-08-14 14:26 ` [uml-devel] " David Howells
2012-08-14 14:31 ` Richard Weinberger
2012-08-14 14:31 ` [uml-devel] " Richard Weinberger
2012-08-14 14:51 ` David Howells
2012-08-14 14:51 ` [uml-devel] " David Howells
2012-08-14 14:54 ` David Howells
2012-08-14 14:54 ` David Howells
2012-08-14 14:54 ` [uml-devel] " David Howells
2012-08-14 14:57 ` Richard Weinberger
2012-08-14 14:57 ` [uml-devel] " Richard Weinberger
2012-08-14 15:06 ` David Howells
2012-08-14 15:06 ` [uml-devel] " David Howells
2012-08-14 15:08 ` Richard Weinberger
2012-08-14 15:08 ` [uml-devel] " Richard Weinberger
2012-08-14 15:15 ` David Howells
2012-08-14 15:15 ` [uml-devel] " David Howells
2012-08-14 15:17 ` Richard Weinberger
2012-08-14 15:17 ` [uml-devel] " Richard Weinberger
2012-08-14 17:41 ` Randy Dunlap
2012-08-20 2:51 ` Rusty Russell
2012-08-20 2:51 ` [uml-devel] " Rusty Russell
2012-08-21 17:43 ` Randy Dunlap
2012-08-22 1:17 ` Rusty Russell
2012-08-14 15:09 ` David Howells
2012-08-14 15:09 ` David Howells
2012-08-14 15:09 ` [uml-devel] " David Howells
2012-08-14 14:54 ` Richard Weinberger
2012-08-14 14:54 ` [uml-devel] " Richard Weinberger
2012-07-26 15:43 ` linux-next: Tree for July 26 (vfio) Randy Dunlap
2012-07-26 16:16 ` Alex Williamson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a9xys53h.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=richard@nod.at \
--cc=sfr@canb.auug.org.au \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.