From: Randy Dunlap <rdunlap@xenotime.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Richard Weinberger <richard@nod.at>,
user-mode-linux-devel@lists.sourceforge.net
Subject: Re: linux-next: Tree for July 26 (uml)
Date: Thu, 26 Jul 2012 08:18:39 -0700 [thread overview]
Message-ID: <50115FCF.4060708@xenotime.net> (raw)
In-Reply-To: <20120726150419.0de645e8750e3a15fa0f1aaa@canb.auug.org.au>
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
--
~Randy
next prev parent reply other threads:[~2012-07-26 15:18 UTC|newest]
Thread overview: 21+ 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 ` Randy Dunlap [this message]
2012-08-13 17:00 ` linux-next: Tree for July 26 (uml) Randy Dunlap
2012-08-14 0:13 ` Rusty Russell
2012-08-14 14:26 ` David Howells
2012-08-14 14:31 ` Richard Weinberger
2012-08-14 14:51 ` David Howells
2012-08-14 14:54 ` Richard Weinberger
2012-08-14 14:54 ` David Howells
2012-08-14 14:57 ` Richard Weinberger
2012-08-14 15:06 ` David Howells
2012-08-14 15:08 ` Richard Weinberger
2012-08-14 15:15 ` David Howells
2012-08-14 15:17 ` Richard Weinberger
2012-08-14 17:41 ` Randy Dunlap
2012-08-20 2:51 ` Rusty Russell
2012-08-21 17:43 ` Randy Dunlap
2012-08-22 1:17 ` Rusty Russell
2012-08-14 15:09 ` David Howells
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=50115FCF.4060708@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).