From: Jaswinder Singh Rajput <jaswinder@kernel.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Cyrill Gorcunov <gorcunov@gmail.com>, 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
Subject: Re: [git-pull -tip] fix headers_check warnings
Date: Mon, 02 Feb 2009 23:42:49 +0530 [thread overview]
Message-ID: <1233598369.10133.6.camel@localhost.localdomain> (raw)
In-Reply-To: <4987321A.1020404@zytor.com>
On Mon, 2009-02-02 at 09:49 -0800, H. Peter Anvin wrote:
> Jaswinder Singh Rajput wrote:
> >>
> >> 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...
> >
> > No, you cannot remove sys_arch_prctl otherwise you will get sparse
> > warning like this:
> >
> > CHECK arch/x86/kernel/process_64.c
> > arch/x86/kernel/process_64.c:833:6: warning: symbol 'sys_arch_prctl' was not declared. Should it be static?
> >
>
> Perhaps we can just move this prototype to <asm/syscalls.h>.
>
fixed and send git pull V2.
--
JSR
next prev parent reply other threads:[~2009-02-02 18:12 UTC|newest]
Thread overview: 9+ 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 16:56 ` Jaswinder Singh Rajput
2009-02-02 17:21 ` Cyrill Gorcunov
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 [this message]
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=1233598369.10133.6.camel@localhost.localdomain \
--to=jaswinder@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=gorcunov@gmail.com \
--cc=hpa@zytor.com \
--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 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.