From: Stephen Boyd <swboyd@chromium.org>
To: Geert Uytterhoeven <geert+renesas@glider.be>,
Mark Brown <broonie@kernel.org>
Cc: linux-spi@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
linux-kernel@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: Re: [PATCH] spi: rspi: Use platform_get_irq_byname_optional() for optional irqs
Date: Wed, 16 Oct 2019 16:25:57 -0700 [thread overview]
Message-ID: <5da7a706.1c69fb81.7818.0cfe@mx.google.com> (raw)
In-Reply-To: <20191016143101.28738-1-geert+renesas@glider.be>
Quoting Geert Uytterhoeven (2019-10-16 07:31:01)
> As platform_get_irq_byname() now prints an error when the interrupt
> does not exist, scary warnings may be printed for optional interrupts:
>
> renesas_spi e6b10000.spi: IRQ rx not found
> renesas_spi e6b10000.spi: IRQ mux not found
>
> Fix this by calling platform_get_irq_byname_optional() instead.
> Remove the no longer needed printing of platform_get_irq errors, as the
> remaining calls to platform_get_irq() and platform_get_irq_byname() take
> care of that.
>
> 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>
next prev parent reply other threads:[~2019-10-16 23:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-16 14:31 [PATCH] spi: rspi: Use platform_get_irq_byname_optional() for optional irqs Geert Uytterhoeven
2019-10-16 23:25 ` Stephen Boyd [this message]
2019-10-18 18:07 ` Applied "spi: rspi: Use platform_get_irq_byname_optional() for optional irqs" to the spi tree Mark Brown
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=5da7a706.1c69fb81.7818.0cfe@mx.google.com \
--to=swboyd@chromium.org \
--cc=broonie@kernel.org \
--cc=geert+renesas@glider.be \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-spi@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).