public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp•com.au>
To: Randy Dunlap <rdunlap@xenotime•net>
Cc: Richard Weinberger <richard@nod•at>,
	David Howells <dhowells@redhat•com>,
	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: Wed, 22 Aug 2012 10:47:35 +0930	[thread overview]
Message-ID: <874nnv3ets.fsf@rustcorp.com.au> (raw)
In-Reply-To: <5033C8DF.2080403@xenotime.net>

On Tue, 21 Aug 2012 10:43:59 -0700, Randy Dunlap <rdunlap@xenotime•net> wrote:
> On 08/19/2012 07:51 PM, Rusty Russell wrote:
> 
> > On Tue, 14 Aug 2012 10:41:42 -0700, Randy Dunlap <rdunlap@xenotime•net> wrote:
> >> On 08/14/2012 08:17 AM, Richard Weinberger wrote:
> >>
> >>> Am 14.08.2012 17:15, schrieb David Howells:
> >>>> How about this then?
> >>>>
> >>>> David
> >>>> ---
> >>>> diff --git a/arch/x86/um/Kconfig b/arch/x86/um/Kconfig
> >>>> index 9926e11..a4b0c10 100644
> >>>> --- a/arch/x86/um/Kconfig
> >>>> +++ b/arch/x86/um/Kconfig
> >>>> @@ -21,9 +21,11 @@ config 64BIT
> >>>>  config X86_32
> >>>>  	def_bool !64BIT
> >>>>  	select HAVE_AOUT
> >>>> +	select MODULES_USE_ELF_REL
> >>>>  
> >>>>  config X86_64
> >>>>  	def_bool 64BIT
> >>>> +	select MODULES_USE_ELF_RELA
> >>>>  
> >>>>  config RWSEM_XCHGADD_ALGORITHM
> >>>>  	def_bool X86_XADD && 64BIT
> >>>
> >>> Looks sane.
> >>>
> >>> Acked-by: Richard Weinberger <richard@nod•at>
> >>
> >>
> >> Acked-by: Randy Dunlap <rdunlap@xenotime•net>
> > 
> > Thanks, folded into David's original patch.
> 
> 
> When will this be fixed in linux-next?
> 
> linux-next of 20120821 still fails.

Should be in latest, ie. 20120822.

Cheers,
Rusty.

  reply	other threads:[~2012-08-22  1:17 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             ` 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 [this message]
2012-08-14 15:09                   ` David Howells
2012-08-14 14:54             ` 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=874nnv3ets.fsf@rustcorp.com.au \
    --to=rusty@rustcorp$(echo .)com.au \
    --cc=dhowells@redhat$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=rdunlap@xenotime$(echo .)net \
    --cc=richard@nod$(echo .)at \
    --cc=sfr@canb$(echo .)auug.org.au \
    --cc=user-mode-linux-devel@lists$(echo .)sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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