linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: David Howells <dhowells@redhat.com>
Cc: 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 16:57:29 +0200	[thread overview]
Message-ID: <502A6759.3090802@nod.at> (raw)
In-Reply-To: <18600.1344956051@warthog.procyon.org.uk>

[-- Attachment #1: Type: text/plain, Size: 792 bytes --]

Am 14.08.2012 16:54, schrieb David Howells:
> David Howells <dhowells@redhat.com> wrote:
> 
>> 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 attached patch works.
> 
> David
> ---
> diff --git a/arch/um/Kconfig.common b/arch/um/Kconfig.common
> index cb837c2..0463e48 100644
> --- a/arch/um/Kconfig.common
> +++ b/arch/um/Kconfig.common
> @@ -11,6 +11,8 @@ config UML
>  	select GENERIC_CPU_DEVICES
>  	select GENERIC_IO
>  	select GENERIC_CLOCKEVENTS
> +	select MODULES_USE_ELF_REL if X86_32
> +	select MODULES_USE_ELF_RELA if X86_64

I think arch/x86/um/Kconfig makes more sense.

Thanks,
//richard


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

  reply	other threads:[~2012-08-14 14:57 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
2012-08-14 14:54         ` Richard Weinberger
2012-08-14 14:54       ` David Howells
2012-08-14 14:57         ` Richard Weinberger [this message]
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=502A6759.3090802@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;
as well as URLs for NNTP newsgroup(s).