public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: the arch/x86 maintainers <x86@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86 headers: remove duplicate pud_large() definition
Date: Fri, 13 Feb 2009 08:27:18 -0800	[thread overview]
Message-ID: <49959F66.5090100@goop.org> (raw)
In-Reply-To: <20090213121858.GB5483@elte.hu>

Ingo Molnar wrote:
>         arch/x86/mach-voyager/voyager_smp.c
>         arch/x86/mm/fault.c
>   

I'm not sure where these two came from.  I certainly didn't touch those 
files; they must have diverged somewhere else along their history.

> and this in kmemcheck:
>
>     Merge branch 'x86/headers' into kmemcheck
>     
>     Conflicts:
>         arch/x86/include/asm/pgtable.h
>     
>     Merged into:
>     
>         arch/x86/include/asm/pgtable_types.h
>     
> Plus the fixlet below.
>
> 	Ingo
>
> ------------------------->
> From 999c7880cc8eeb0cbe6610b8c6d0ab0ec51cd848 Mon Sep 17 00:00:00 2001
> From: Ingo Molnar <mingo@elte.hu>
> Date: Fri, 13 Feb 2009 13:15:55 +0100
> Subject: [PATCH] x86 headers: remove duplicate pud_large() definition
>
> Signed-off-by: Ingo Molnar <mingo@elte.hu>
> ---
>  arch/x86/include/asm/pgtable.h |    7 -------
>  1 files changed, 0 insertions(+), 7 deletions(-)
>
> diff --git a/arch/x86/include/asm/pgtable.h b/arch/x86/include/asm/pgtable.h
> index 62024ff..1c097a3 100644
> --- a/arch/x86/include/asm/pgtable.h
> +++ b/arch/x86/include/asm/pgtable.h
> @@ -387,13 +387,6 @@ static inline unsigned long pages_to_mb(unsigned long npg)
>  #define io_remap_pfn_range(vma, vaddr, pfn, size, prot)	\
>  	remap_pfn_range(vma, vaddr, pfn, size, prot)
>  
> -#if PAGETABLE_LEVELS == 2
> -static inline int pud_large(pud_t pud)
> -{
> -	return 0;
> -}
> -#endif
>   

OK.

    J

  parent reply	other threads:[~2009-02-13 16:27 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-11 23:23 [GIT PULL] clean header untangling Jeremy Fitzhardinge
2009-02-13 12:02 ` Ingo Molnar
2009-02-13 12:18   ` [PATCH] x86 headers: remove duplicate pud_large() definition Ingo Molnar
2009-02-13 12:23     ` [PATCH] x86 headers: include linux/types.h Ingo Molnar
2009-02-13 12:27       ` Ingo Molnar
2009-02-13 12:37         ` [PATCH] x86 headers: protect page_32.h via __ASSEMBLY__ Ingo Molnar
2009-02-13 18:44           ` Jeremy Fitzhardinge
2009-02-13 18:49             ` Ingo Molnar
2009-02-13 18:52               ` Jeremy Fitzhardinge
2009-02-13 18:57                 ` Ingo Molnar
2009-02-13 16:25         ` [PATCH] x86 headers: include linux/types.h Jeremy Fitzhardinge
2009-02-13 18:09           ` Ingo Molnar
2009-02-16 21:00             ` Jeremy Fitzhardinge
2009-02-13 18:52       ` Jeremy Fitzhardinge
2009-02-13 18:55         ` Ingo Molnar
2009-02-13 18:59           ` Jeremy Fitzhardinge
2009-02-13 20:05             ` Ingo Molnar
2009-02-13 18:57         ` Jaswinder Singh Rajput
2009-02-13 16:27     ` Jeremy Fitzhardinge [this message]
2009-02-13 18:02       ` [PATCH] x86 headers: remove duplicate pud_large() definition 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=49959F66.5090100@goop.org \
    --to=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=x86@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