mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Compile errors on 32-bit build due to d4bbf7e7759afc172e2bfbc5c416324590049cdd
Date: Mon, 9 Jan 2012 08:39:10 -0800	[thread overview]
Message-ID: <20120109163910.GA21732@google.com> (raw)
In-Reply-To: <20120108024029.GA17214@phenom.dumpdata.com>

Hello, Konrad.

On Sat, Jan 07, 2012 at 09:40:29PM -0500, Konrad Rzeszutek Wilk wrote:
> Hey Tejun
> 
> Your patch titled " Merge branch 'master' into x86/memblock" breaks compilation
> under 32-bit with CONFIG_XEN=y.
> 
> /home/konrad/linux-linus/arch/x86/xen/mmu.c: In function ‘xen_setup_kernel_pagetable’:
> /home/konrad/linux-linus/arch/x86/xen/mmu.c:1855: error: expected ‘;’ before ‘)’ token
> /home/konrad/linux-linus/arch/x86/xen/mmu.c:1855: error: expected statement before ‘)’ token
> 
> Looking at merge it looks like you added an extra ')'?
> 
> This patch below fixes it, which I was thinking to attach it to my tree that I will
> send on Monday to Linus.
> 
> From 18ae9edebde83ef358e997e319868d664fb2ddb8 Mon Sep 17 00:00:00 2001
> From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
> Date: Sat, 7 Jan 2012 21:27:38 -0500
> Subject: [PATCH] xen/mmu: Fix compile errors introduced by x86/memblock mismerge.
> MIME-Version: 1.0
> Content-Type: text/plain; charset=UTF-8
> Content-Transfer-Encoding: 8bit
> 
> The git commit d4bbf7e7759afc172e2bfbc5c416324590049cdd
> "Merge branch 'master' into x86/memblock" mismerged the 32-bit
> section causing:
> 
> arch/x86/xen/mmu.c: In function ‘xen_setup_kernel_pagetable’:
> arch/x86/xen/mmu.c:1855: error: expected ‘;’ before ‘)’ token
> arch/x86/xen/mmu.c:1855: error: expected statement before ‘)’ token
> 
> Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
> ---
>  arch/x86/xen/mmu.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/arch/x86/xen/mmu.c b/arch/x86/xen/mmu.c
> index f4bf8aa..58a0e46 100644
> --- a/arch/x86/xen/mmu.c
> +++ b/arch/x86/xen/mmu.c
> @@ -1852,7 +1852,7 @@ pgd_t * __init xen_setup_kernel_pagetable(pgd_t *pgd,
>  	xen_write_cr3(__pa(initial_page_table));
>  
>  	memblock_reserve(__pa(xen_start_info->pt_base),
> -			 xen_start_info->nr_pt_frames * PAGE_SIZE));
> +			 xen_start_info->nr_pt_frames * PAGE_SIZE);

Oops, how did that get through?  Sorry about that.

 Acked-by: Tejun Heo <tj@kernel.org>

Thank you.

-- 
tejun

      reply	other threads:[~2012-01-09 16:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-08  2:40 Konrad Rzeszutek Wilk
2012-01-09 16:39 ` Tejun Heo [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=20120109163910.GA21732@google.com \
    --to=tj@kernel.org \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    /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

Powered by JetHome