public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-pcmcia@lists.infradead.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	oss@buserror.net, linuxppc-dev@ozlabs.org,
	Claudiu Manoil <claudiu.manoil@nxp.com>,
	qiang.zhao@nxp.com
Subject: Re: [PATCH] drivers/pcmcia: NO_IRQ removal for electra_cf.c
Date: Thu, 16 Mar 2017 20:55:32 +1100	[thread overview]
Message-ID: <877f3plf57.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <CAK8P3a2TzAdOnyOyS5ZbQK5WRkNKnGxLc=7SYjw_Y75VdbnyZw@mail.gmail.com>

Arnd Bergmann <arnd@arndb.de> writes:
> On Wed, Mar 15, 2017 at 6:35 AM, Michael Ellerman <mpe@ellerman.id.au> wrote:
>> I'll do patches for everything above that's not drivers/soc or
>> include/soc and hopefully we can hear from someone at NXP on the plans
>> for getting the soc parts enabled on arm.
>
> I think the removal of the NO_IRQ references is a requirement for
> getting the drivers working properly on ARM, as the OF platform
> code will use '0' for invalid IRQs.

OK. So the #define NO_IRQ (-1) in arch/arm/include/asm/irq.h is a red
herring and should be ignored for anything modern?

cheers

  reply	other threads:[~2017-03-16  9:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-10 10:01 [PATCH] drivers/pcmcia: NO_IRQ removal for electra_cf.c Michael Ellerman
2017-03-14 10:51 ` Michael Ellerman
2017-03-14 12:47   ` Arnd Bergmann
2017-03-15  5:35     ` Michael Ellerman
2017-03-15 12:07       ` Arnd Bergmann
2017-03-16  9:55         ` Michael Ellerman [this message]
2017-03-16 10:05           ` Arnd Bergmann
2017-03-15 17:50       ` Scott Wood
2017-03-16  9:53         ` Michael Ellerman
2017-03-21 11:36 ` Michael Ellerman

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=877f3plf57.fsf@concordia.ellerman.id.au \
    --to=mpe@ellerman.id.au \
    --cc=arnd@arndb.de \
    --cc=claudiu.manoil@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pcmcia@lists.infradead.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=oss@buserror.net \
    --cc=qiang.zhao@nxp.com \
    /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