public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Jaswinder Singh Rajput <jaswinder@kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>, x86 maintainers <x86@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Sam Ravnborg <sam@ravnborg.org>,
	David Miller <davem@davemloft.net>,
	LKML <linux-kernel@vger.kernel.org>,
	reiserfs-devel@vger.kernel.org, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [git-pull -tip] fix headers_check warnings
Date: Mon, 2 Feb 2009 20:21:59 +0300	[thread overview]
Message-ID: <20090202172159.GA7479@localhost> (raw)
In-Reply-To: <1233593765.3244.14.camel@localhost.localdomain>

[Jaswinder Singh Rajput - Mon, Feb 02, 2009 at 10:26:05PM +0530]
| Ingo,
| 
| The following changes since commit 1ff8f739c7cc4eaa89b6ba986494f458ff7bdbef:
|   Jaswinder Singh Rajput (1):
|         headers_check fix: xtensa, swab.h
| 
| are available in the git repository at:
| 
|   git://git.kernel.org/pub/scm/linux/kernel/git/jaswinder/linux-2.6-tipclean.git core/header-fixes
| 
| Jaswinder Singh Rajput (7):
|       headers_check fix: linux/coda_psdev.h
|       headers_check fix: linux/in6.h
|       headers_check fix: linux/nubus.h
|       headers_check fix: linux/socket.h
|       headers_check fix: linux/reinserfs_fs.h
|       headers_check fix: x86, prctl.h
|       headers_check fix: x86, setup.h
| 
|  arch/x86/include/asm/prctl.h |    6 +++-
|  arch/x86/include/asm/setup.h |   45 ++++++++++++++++++++---------------------
|  include/linux/coda_psdev.h   |   15 ++++++-------
|  include/linux/in6.h          |    2 +-
|  include/linux/nubus.h        |    2 +
|  include/linux/reiserfs_fs.h  |    8 +++++++
|  include/linux/socket.h       |    6 +++-
|  7 files changed, 48 insertions(+), 36 deletions(-)
| 
...
| 
| Complete diff:
| diff --git a/arch/x86/include/asm/prctl.h b/arch/x86/include/asm/prctl.h
| index a889464..fdbeb85 100644
| --- a/arch/x86/include/asm/prctl.h
| +++ b/arch/x86/include/asm/prctl.h
| @@ -6,8 +6,10 @@
|  #define ARCH_GET_FS 0x1003
|  #define ARCH_GET_GS 0x1004
|  
| -#ifdef CONFIG_X86_64
| +#ifdef __KERNEL__
| +# ifdef CONFIG_X86_64
|  extern long sys_arch_prctl(int, unsigned long);
| -#endif /* CONFIG_X86_64 */
| +# endif /* CONFIG_X86_64 */
| +#endif /* __KERNEL__ */
| 
...

Hi Jaswinder,

it seems we have a clash here :) I thought this part
was just dropped out

	http://lkml.org/lkml/2009/1/14/461

and Peter had been applying it on tip:x86/header-fixes

	http://lkml.org/lkml/2009/1/14/549

but maybe it's just lost...

		-- Cyrill --

  reply	other threads:[~2009-02-02 17:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-02 16:56 [git-pull -tip] fix headers_check warnings Jaswinder Singh Rajput
2009-02-02 17:21 ` Cyrill Gorcunov [this message]
2009-02-02 17:30   ` Jaswinder Singh Rajput
2009-02-02 17:49     ` H. Peter Anvin
2009-02-02 17:53       ` Cyrill Gorcunov
2009-02-02 18:12       ` Jaswinder Singh Rajput
2009-02-02 17:49 ` Arnd Bergmann
2009-02-03 14:37   ` Jaswinder Singh Rajput

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=20090202172159.GA7479@localhost \
    --to=gorcunov@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=hpa@zytor.com \
    --cc=jaswinder@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=reiserfs-devel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    --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