linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Max Filippov <jcmvbkbc@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Chris Zankel <chris@zankel.net>,
	Marc Gauthier <marc@tensilica.com>,
	Baruch Siach <baruch@tkos.co.il>,
	"linux-xtensa@linux-xtensa.org" <linux-xtensa@linux-xtensa.org>,
	Linux-Arch <linux-arch@vger.kernel.org>
Subject: Re: [PATCH v2] xtensa: define NO_IRQ as 0, remove other definitions
Date: Thu, 12 Sep 2013 11:43:07 +0400	[thread overview]
Message-ID: <CAMo8Bf+_9pqL+2C-BU5e4S9-jkGNbA-cXu_Rc_V8TcEb_n+BgQ@mail.gmail.com> (raw)
In-Reply-To: <CAMuHMdVko5v2vma+spq_XhzaESVNOT5PdBgmEgFZQhRXamNhmw@mail.gmail.com>

On Thu, Sep 12, 2013 at 11:26 AM, Geert Uytterhoeven
<geert@linux-m68k.org> wrote:
> On Thu, Sep 12, 2013 at 9:17 AM, Max Filippov <jcmvbkbc@gmail.com> wrote:
>>
>> sound/soc/fsl/fsl_ssi.c: In function 'fsl_ssi_probe':
>> sound/soc/fsl/fsl_ssi.c:939:26: error: 'NO_IRQ' undeclared (first use in this function)
>>
>> Previous definitions (-1) were correct when used as a hardware IRQ number,
>> but are incorrect as a mapped IRQ number.
>>
>> Signed-off-by: Max Filippov <jcmvbkbc@gmail.com>
>> ---
>>  arch/xtensa/include/asm/irq.h                      |    4 ++++
>>  .../platforms/xtfpga/include/platform/hardware.h   |    4 ----
>>  arch/xtensa/variants/s6000/include/variant/irq.h   |    1 -
>>  3 files changed, 4 insertions(+), 5 deletions(-)
>
> Shouldn't sound/soc/fsl/fsl_ssi.c be changed instead:
>
> -if (ssi_private->irq == NO_IRQ) {
> +if (!ssi_private->irq) {

I agree, this needs to be fixed too.

> Cfr. the thread https://lkml.org/lkml/2013/7/25/642

I saw that thread and I don't see that patch applied anywhere.

Thanks.
-- Max

      reply	other threads:[~2013-09-12  7:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-12  7:17 [PATCH v2] xtensa: define NO_IRQ as 0, remove other definitions Max Filippov
2013-09-12  7:26 ` Geert Uytterhoeven
2013-09-12  7:43   ` Max Filippov [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=CAMo8Bf+_9pqL+2C-BU5e4S9-jkGNbA-cXu_Rc_V8TcEb_n+BgQ@mail.gmail.com \
    --to=jcmvbkbc@gmail.com \
    --cc=baruch@tkos.co.il \
    --cc=chris@zankel.net \
    --cc=geert@linux-m68k.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-xtensa@linux-xtensa.org \
    --cc=marc@tensilica.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;
as well as URLs for NNTP newsgroup(s).