From: Ingo Molnar <mingo@elte.hu>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Jaswinder Singh Rajput <jaswinder@kernel.org>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Jaswinder Singh Rajput <jaswinderlinux@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Sam Ravnborg <sam@ravnborg.org>,
Andrew Morton <akpm@linux-foundation.org>,
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 17:01:00 +0100 [thread overview]
Message-ID: <20090206160100.GS18368@elte.hu> (raw)
In-Reply-To: <20090206154917.GE13758@n2100.arm.linux.org.uk>
* Russell King - ARM Linux <linux@arm.linux.org.uk> wrote:
> On Fri, Feb 06, 2009 at 04:45:39PM +0100, Ingo Molnar wrote:
> >
> > * Russell King - ARM Linux <linux@arm.linux.org.uk> wrote:
> >
> > > On Fri, Feb 06, 2009 at 08:59:01PM +0530, Jaswinder Singh Rajput wrote:
> > > > Jaswinder Singh Rajput (2):
> > > > Neither asm/types.h nor linux/types.h is required for arch/ia64/include/asm/fpu.h
> > > > make linux/types.h as assembly safe
> > >
> > > I continue to disagree with the need for the second patch.
> >
> > But have not replied to my mail about that so far.
>
> Sigh. No I didn't - because I also got a reply from Jaswinder and
> covered all points in _that_ reply.
>
> Would you like me to re-send my reply so that you can appear in the To:
> header?
>
> Stop making this discussion stupidly obtuse.
I am not making anything stupidly obtuse, your reply to Jaswinder was in a
different (but related) portion of the thread, that i have not read yet at
that point. I have read it now and have replied.
Ingo
next prev parent reply other threads:[~2009-02-06 16:01 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 ` [PATCH] " Ingo Molnar
2009-02-06 15:29 ` [linux-next][PATCH] " 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 [this message]
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=20090206160100.GS18368@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=chris@zankel.net \
--cc=cooloney@kernel.org \
--cc=dhowells@redhat.com \
--cc=hskinnemoen@atmel.com \
--cc=jaswinder@kernel.org \
--cc=jaswinderlinux@gmail.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=matthew@wil.cx \
--cc=ralf@linux-mips.org \
--cc=sam@ravnborg.org \
--cc=tony.luck@intel.com \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).