[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTimC1kBuAvd_kei8cdWvgzL-u8FdfEfEGZH1t2ZM@mail.gmail.com>
Date: Wed, 8 Sep 2010 16:28:07 -0400
From: Mike Frysinger <vapier.adi@...il.com>
To: James Bottomley <James.Bottomley@...senpartnership.com>
Cc: Thomas Gleixner <tglx@...utronix.de>,
LKML <linux-kernel@...r.kernel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Ingo Molnar <mingo@...e.hu>,
Peter Zijlstra <peterz@...radead.org>,
Christoph Hellwig <hch@...radead.org>,
linux-alpha@...r.kernel.org, linux-cris-kernel@...s.com,
Haavard Skinnemoen <hskinnemoen@...el.com>,
Tony Luck <tony.luck@...el.com>, linux-ia64@...r.kernel.org,
Yoshinori Sato <ysato@...rs.sourceforge.jp>,
Hirokazu Takata <takata@...ux-m32r.org>,
Greg Ungerer <gerg@...inux.org>, Jeff Dike <jdike@...toit.com>,
linux-parisc@...r.kernel.org, Chris Zankel <chris@...kel.net>,
linux-arch@...r.kernel.org
Subject: Re: [RFC trollpatch 1/1] genirq: Remove the fits all and nothing
__do_IRQ() code
On Wed, Sep 8, 2010 at 14:51, James Bottomley wrote:
> On Wed, 2010-09-08 at 18:14 +0000, Thomas Gleixner wrote:
>> plain text document attachment (genirq-troll-patch.patch)
>> __do_IRQ() has been deprecated after a two years migration phase in
>> commit 0e57aa1. Since then another 18 month have gone by.
>>
>> So here's the status three and a half years after the flow based
>> infrastructure was merged:
>>
>> The following architectures are still using __do_IRQ():
>>
>> alpha, cris, ia64, h8300, m32r, m68knommu, parisc, um
>>
>> So now the question arises what to do with __do_IRQ().
>>
>> Removing it would be the right thing, but that'll break 8 archs, so
>> it's probably not considered a good idea, though for most of them the
>> conversion should be reasonably trivial.
>>
>> I'm happy to move that code into kernel/irq/cruft.c forever if there
>> is no way to get the remaining users converted in the forseeable
>> future. It looks like they can cope with the annoying build warning
>> nicely.
>
> Well, if you're going to deprecate something that 8 architectures rely
> on, it would be nice to tell people ... or even just linux-arch ... most
> of us do read that. I've actually never noticed the warning the commit
> activated in any of my parisc compiles for some reason.
the only reason Blackfin was converted quickly is because the code
issues a warning (that has been there for a long time):
# warning __do_IRQ is deprecated. Please convert to proper flow handlers
so i guess you're saying that you disable the "ENABLE_WARN_DEPRECATED"
option ? or you dont pay attention to warnings when compiling kernels
?
-mike
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists