From: Stephen Boyd <swboyd@chromium.org>
To: Geert Uytterhoeven <geert+renesas@glider.be>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.com>
Cc: linux-renesas-soc@vger.kernel.org, linux-serial@vger.kernel.org,
linux-kernel@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: Re: [PATCH] serial: sh-sci: Use platform_get_irq_optional() for optional interrupts
Date: Thu, 03 Oct 2019 09:10:16 -0700 [thread overview]
Message-ID: <5d961d69.1c69fb81.43b1b.addf@mx.google.com> (raw)
In-Reply-To: <20191001180743.1041-1-geert+renesas@glider.be>
Quoting Geert Uytterhoeven (2019-10-01 11:07:43)
> As platform_get_irq() now prints an error when the interrupt does not
> exist, scary warnings may be printed for optional interrupts:
>
> sh-sci e6550000.serial: IRQ index 1 not found
> sh-sci e6550000.serial: IRQ index 2 not found
> sh-sci e6550000.serial: IRQ index 3 not found
> sh-sci e6550000.serial: IRQ index 4 not found
> sh-sci e6550000.serial: IRQ index 5 not found
>
> Fix this by calling platform_get_irq_optional() instead for all but the
> first interrupts, which are optional.
>
> Fixes: 7723f4c5ecdb8d83 ("driver core: platform: Add an error message to platform_get_irq*()")
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
Reviewed-by: Stephen Boyd <swboyd@chromium.org>
prev parent reply other threads:[~2019-10-03 16:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-01 18:07 [PATCH] serial: sh-sci: Use platform_get_irq_optional() for optional interrupts Geert Uytterhoeven
2019-10-02 4:49 ` Yoshihiro Shimoda
2019-10-02 9:52 ` kbuild test robot
2019-10-02 11:28 ` Geert Uytterhoeven
2019-10-02 14:20 ` [kbuild-all] " Chen, Rong A
2019-10-03 16:10 ` Stephen Boyd [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=5d961d69.1c69fb81.43b1b.addf@mx.google.com \
--to=swboyd@chromium.org \
--cc=geert+renesas@glider.be \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
/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).