All of lore.kernel.org
 help / color / mirror / Atom feed
From: Harvey Harrison <harvey.harrison@gmail.com>
To: Alexander van Heukelum <heukelum@mailshack.com>
Cc: Ingo Molnar <mingo@elte.hu>, Andi Kleen <andi@firstfloor.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Alexander van Heukelum <heukelum@fastmail.fm>
Subject: Re: [PATCH] Build fix for uml/x86_64
Date: Fri, 04 Apr 2008 12:00:10 -0700	[thread overview]
Message-ID: <1207335610.18838.85.camel@brick> (raw)
In-Reply-To: <20080404185147.GB8989@mailshack.com>

On Fri, 2008-04-04 at 20:51 +0200, Alexander van Heukelum wrote:
> Build fix for uml/x86_64, which was broken by:
> x86: remove x86-specific implementations of find_first_bit
> 
> Signed-off-by: Alexander van Heukelum <heukelum@fastmail.fm>
> 
> ---
> 
> Hi Ingo,
> 
> I broke uml again :(
> 
> This patch fixes the problem for x86_64. These changes
> should have been included in:
> 
> x86: switch x86_64 to generic find_first_bit
> 
> Greetings,
>         Alexander
> 
>  arch/um/Kconfig.x86_64      |    4 ++++
>  arch/um/sys-x86_64/Makefile |    2 +-
>  2 files changed, 5 insertions(+), 1 deletions(-)
> 
> diff --git a/arch/um/Kconfig.x86_64 b/arch/um/Kconfig.x86_64
> index a29f545..84cefd5 100644
> --- a/arch/um/Kconfig.x86_64
> +++ b/arch/um/Kconfig.x86_64
> @@ -31,6 +31,10 @@ config SMP_BROKEN
>  	bool
>  	default y
>  
> +config GENERIC_FIND_FIRST_BIT
> +	bool
> +	default y
> +
	def_bool y

Cheers,

Harvey



  reply	other threads:[~2008-04-04 19:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-04 18:49 [PATCH] x86: finalize bitops unification Alexander van Heukelum
2008-04-04 18:51 ` [PATCH] Build fix for uml/i386 Alexander van Heukelum
2008-04-04 18:51 ` [PATCH] Build fix for uml/x86_64 Alexander van Heukelum
2008-04-04 19:00   ` Harvey Harrison [this message]
2008-04-04 20:40     ` [PATCH] uml: cleanup: use def_bool in Kconfig files Alexander van Heukelum
2008-04-07  7:00 ` [PATCH] x86: finalize bitops unification Ingo Molnar

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=1207335610.18838.85.camel@brick \
    --to=harvey.harrison@gmail.com \
    --cc=andi@firstfloor.org \
    --cc=heukelum@fastmail.fm \
    --cc=heukelum@mailshack.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.