DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=pacbell.net;
  h=Received:X-YMail-OSG:X-Yahoo-Newman-Property:From:To:Subject:Date:User-Agent:Cc:References:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Content-Disposition:Message-Id;
  b=b9SJWzj3N3uE+iaejNoSPvZFHIQ71AlPtAvhFBAaqxy9DNL131U0rtmgcmvbxo+eRIs4vgI8MdNIFOyRjjYREt6zD/DGJXIfvZ1PBSqgvINu7a1I/ntvk8aeXT8J9DHRZAf44HqUmR6bJlzlfOgqqp8AR2YJs21+aGpp1neaPXw=  ;
From: David Brownell <david-b@pacbell.net>
To: Robert Hancock <hancockr@shaw.ca>
Subject: Re: [patch] x86 supports NO_IRQ convention
Date: Mon, 23 Jun 2008 23:39:25 -0700
User-Agent: KMail/1.9.9
Cc: benh@kernel.crashing.org, lkml <linux-kernel@vger.kernel.org>,
       Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
       hpa@zytor.com
References: <fa.mcHAIQmpGZB1Vrm7ZD4/q9eo08Y@ifi.uio.no> <fa.EDfpY1oxab2UaliWrUY0jyr5T1k@ifi.uio.no> <486059F9.6060901@shaw.ca>
In-Reply-To: <486059F9.6060901@shaw.ca>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200806232339.25926.david-b@pacbell.net>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 723
Lines: 19

On Monday 23 June 2008, Robert Hancock wrote:
> IRQ 0 is only used by 
> architecture-specific code and is not sharable,

That seems to be the consensus, and it does reflect
how it's used on all architectures I happen to have
seen it in use.

Leaving the question then of what should happen to
the existing NO_IRQ code ... none of the declarations
seems to have a comment "deprecated, don't use this"
and most of the defined values are nonzero.

Some docs appear to be missing.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/