linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Andrew Morton <akpm@osdl.org>,
	torvalds@osdl.org, linux-kernel@vger.kernel.org,
	uclinux-v850@lsi.nec.co.jp
Subject: Re: [RFC: 2.6 patch] include/linux/irq.h: #include <linux/smp.h>
Date: Wed, 21 Dec 2005 23:33:29 +0100	[thread overview]
Message-ID: <20051221223329.GB3917@stusta.de> (raw)
In-Reply-To: <20051221222131.GL1736@flint.arm.linux.org.uk>

On Wed, Dec 21, 2005 at 10:21:31PM +0000, Russell King wrote:
> 
> The point is _exactly_ as the above quotation between Andrew Morton
> and myself.  I'm sure it's not me being thick because it's absolutely
> damned obvious from the above.
> 
> Andrew said: "Yes, it's basically always wrong to include asm/foo.h
> when linux/foo.h exists."
> 
> That statement is a rule.  I assert that this is an incorrect statement
> and I assert that there is a proven case where this statement is incorrect.
> 
> Hence, to avoid people reading Andrew's misleading statement, I followed
> up on precisely _that_ point and _that_ point alone.

OK, now I got it:

You are arguing only against Andrew's statement of a general rule,
not against my patch.

Sorry for my misunderstading.

> Russell King

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


      reply	other threads:[~2005-12-21 22:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-21  1:27 [RFC: 2.6 patch] include/linux/irq.h: #include <linux/smp.h> Adrian Bunk
2005-12-21 10:41 ` Andrew Morton
2005-12-21 11:04   ` Russell King
2005-12-21 21:33     ` Adrian Bunk
2005-12-21 21:48       ` Russell King
2005-12-21 22:11         ` Adrian Bunk
2005-12-21 22:21           ` Russell King
2005-12-21 22:33             ` Adrian Bunk [this message]

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=20051221223329.GB3917@stusta.de \
    --to=bunk@stusta.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.org \
    --cc=uclinux-v850@lsi.nec.co.jp \
    /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).