linux-um archives
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: David Howells <dhowells@redhat.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	user-mode-linux-devel@lists.sourceforge.net,
	Rusty Russell <rusty@rustcorp.com.au>,
	LKML <linux-kernel@vger.kernel.org>,
	Randy Dunlap <rdunlap@xenotime.net>,
	linux-next@vger.kernel.org
Subject: Re: [uml-devel] linux-next: Tree for July 26 (uml)
Date: Tue, 14 Aug 2012 16:54:14 +0200	[thread overview]
Message-ID: <502A6696.4030200@nod.at> (raw)
In-Reply-To: <15981.1344955883@warthog.procyon.org.uk>


[-- Attachment #1.1: Type: text/plain, Size: 628 bytes --]

Am 14.08.2012 16:51, schrieb David Howells:
> 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?

Those are defunct.
AFAIK viro is working on UML/ppc64.

> 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.

The issue happens only on -next, right?
I can have a closer look at the issue tomorrow.

Thanks,
//richard


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

[-- Attachment #2: Type: text/plain, Size: 395 bytes --]

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

[-- Attachment #3: Type: text/plain, Size: 194 bytes --]

_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

      parent reply	other threads:[~2012-08-14 14:54 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20120726150419.0de645e8750e3a15fa0f1aaa@canb.auug.org.au>
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       ` [uml-devel] " David Howells
2012-08-14 14:31         ` Richard Weinberger
2012-08-14 14:51           ` David Howells
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                           ` [uml-devel] " Rusty Russell
2012-08-21 17:43                             ` Randy Dunlap
2012-08-22  1:17                               ` Rusty Russell
2012-08-14 15:09                   ` [uml-devel] " David Howells
2012-08-14 14:54             ` Richard Weinberger [this message]

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=502A6696.4030200@nod.at \
    --to=richard@nod.at \
    --cc=dhowells@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    --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