From: Ingo Molnar <mingo@elte•hu>
To: KOSAKI Motohiro <kosaki.motohiro@jp•fujitsu.com>
Cc: Jaswinder Singh Rajput <jaswinderlinux@gmail•com>,
Jaswinder Singh Rajput <jaswinder@kernel•org>,
Linus Torvalds <torvalds@linux-foundation•org>,
Sam Ravnborg <sam@ravnborg•org>,
Andrew Morton <akpm@linux-foundation•org>,
Russell King - ARM Linux <linux@arm•linux.org.uk>,
hskinnemoen@atmel•com, cooloney@kernel•org, tony.luck@intel•com,
ralf@linux-mips•org, dhowells@redhat•com, matthew@wil•cx,
chris@zankel•net, LKML <linux-kernel@vger•kernel.org>,
linux-next <linux-next@vger•kernel.org>,
linux-ia64 <linux-ia64@vger•kernel.org>
Subject: Re: [PATCH] revert headers_check fix: ia64, fpu.h
Date: Fri, 6 Feb 2009 15:55:56 +0100 [thread overview]
Message-ID: <20090206145556.GH18368@elte.hu> (raw)
In-Reply-To: <20090206180957.6294.KOSAKI.MOTOHIRO@jp.fujitsu.com>
* KOSAKI Motohiro <kosaki.motohiro@jp•fujitsu.com> wrote:
> > > Index: b/arch/ia64/include/asm/fpu.h
> > > ===================================================================
> > > --- a/arch/ia64/include/asm/fpu.h
> > > +++ b/arch/ia64/include/asm/fpu.h
> > > @@ -6,7 +6,7 @@
> > > * David Mosberger-Tang <davidm@hpl•hp.com>
> > > */
> > >
> > > -#include <linux/types.h>
> > > +#include <asm/types.h>
> > >
> >
> > No , we do not even need asm/types.h
> >
> > Subject: [PATCH] Neither asm/types.h nor linux/types.h is not required
> > for arch/ia64/include/asm/fpu.h
> >
> > Signed-off-by: Jaswinder Singh Rajput <jaswinderrajput@gmail•com>
>
> ok. I confirmed.
> Tested-by: KOSAKI Motohiro <kosaki.motohiro@jp•fujitsu.com>
> Reviewed-by: KOSAKI Motohiro <kosaki.motohiro@jp•fujitsu.com>
Thanks.
Jaswinder, mind adding these tags to the commit and sending a pull request
with all fixes?
Ingo
next prev parent reply other threads:[~2009-02-06 14:56 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1233385816.17794.16.camel@localhost.localdomain>
2009-02-06 8:19 ` [linux-next][PATCH] revert headers_check fix: ia64, fpu.h KOSAKI Motohiro
2009-02-06 8:53 ` [PATCH] " Jaswinder Singh Rajput
2009-02-06 9:11 ` [linux-next][PATCH] " KOSAKI Motohiro
2009-02-06 14:55 ` Ingo Molnar [this message]
2009-02-06 15:29 ` Jaswinder Singh Rajput
2009-02-06 15:33 ` Russell King - ARM Linux
2009-02-06 15:45 ` [PATCH] " Ingo Molnar
2009-02-06 15:49 ` Russell King - ARM Linux
2009-02-06 16:01 ` Ingo Molnar
2009-02-06 15:48 ` Jaswinder Singh Rajput
2009-02-06 15:55 ` [linux-next][PATCH] " Russell King - ARM Linux
2009-02-06 16:12 ` Ingo Molnar
2009-02-06 16:23 ` Russell King - ARM Linux
2009-02-06 16:33 ` [PATCH] " Ingo Molnar
2009-02-06 16:38 ` Russell King - ARM Linux
2009-02-06 17:14 ` [linux-next][PATCH] " Ingo Molnar
2009-02-06 17:22 ` Russell King - ARM Linux
2009-02-06 17:32 ` Sam Ravnborg
2009-02-06 17:41 ` Ingo Molnar
2009-02-06 18:53 ` [PATCH] " Luck, Tony
2009-02-06 13:42 ` Sam Ravnborg
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=20090206145556.GH18368@elte.hu \
--to=mingo@elte$(echo .)hu \
--cc=akpm@linux-foundation$(echo .)org \
--cc=chris@zankel$(echo .)net \
--cc=cooloney@kernel$(echo .)org \
--cc=dhowells@redhat$(echo .)com \
--cc=hskinnemoen@atmel$(echo .)com \
--cc=jaswinder@kernel$(echo .)org \
--cc=jaswinderlinux@gmail$(echo .)com \
--cc=kosaki.motohiro@jp$(echo .)fujitsu.com \
--cc=linux-ia64@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux@arm$(echo .)linux.org.uk \
--cc=matthew@wil$(echo .)cx \
--cc=ralf@linux-mips$(echo .)org \
--cc=sam@ravnborg$(echo .)org \
--cc=tony.luck@intel$(echo .)com \
--cc=torvalds@linux-foundation$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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