From: David Howells <dhowells@redhat.com>
To: Richard Weinberger <richard@nod.at>
Cc: dhowells@redhat.com, Rusty Russell <rusty@rustcorp.com.au>,
Randy Dunlap <rdunlap@xenotime.net>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
user-mode-linux-devel@lists.sourceforge.net
Subject: Re: linux-next: Tree for July 26 (uml)
Date: Tue, 14 Aug 2012 15:51:23 +0100 [thread overview]
Message-ID: <15981.1344955883@warthog.procyon.org.uk> (raw)
In-Reply-To: <502A613F.1090600@nod.at>
Richard Weinberger <richard@nod.at> wrote:
> Is there no way to get this information from the UML subarch?
> Which is currently X86_32 or X86_64.
Or ppc or ia64? Or are those defunct?
I can certainly try pasting the lines from x86/Kconfig to uml/Kconfig.common
to switch the REL/RELA bits, but it would be nice to get this from the actual
arch if possible to reduce redundancy.
David
next prev parent reply other threads:[~2012-08-14 14:51 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 ` linux-next: Tree for July 26 (uml) Randy Dunlap
2012-08-13 17:00 ` 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 [this message]
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=15981.1344955883@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=richard@nod.at \
--cc=rusty@rustcorp.com.au \
--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).