From: Jiri Slaby <jirislaby@kernel.org>
To: Christophe Leroy <christophe.leroy@csgroup.eu>,
Laurentiu Tudor <laurentiu.tudor@nxp.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] tty: evh_bytechan: Replace NO_IRQ by 0
Date: Thu, 6 Oct 2022 07:26:41 +0200 [thread overview]
Message-ID: <ec9d6f4e-08fc-1518-3c72-6e5a24c11204@kernel.org> (raw)
In-Reply-To: <23f608ca57e7e19bc7060d3e563de383e0b2b337.1665033575.git.christophe.leroy@csgroup.eu>
On 06. 10. 22, 7:20, Christophe Leroy wrote:
> NO_IRQ is used to check the return of irq_of_parse_and_map().
>
> On some architecture NO_IRQ is 0, on other architectures it is -1.
>
> irq_of_parse_and_map() returns 0 on error, independent of NO_IRQ.
>
> So use 0 instead of using NO_IRQ.
>
> Signed-off-by: Christophe Leroy <christophe.leroy@csgroup.eu>
Reviewed-by: Jiri Slaby <jirislaby@kernel.org>
> ---
> drivers/tty/ehv_bytechan.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/tty/ehv_bytechan.c b/drivers/tty/ehv_bytechan.c
> index 19d32cb6af84..8595483f4697 100644
> --- a/drivers/tty/ehv_bytechan.c
> +++ b/drivers/tty/ehv_bytechan.c
> @@ -118,7 +118,7 @@ static int find_console_handle(void)
> return 0;
>
> stdout_irq = irq_of_parse_and_map(np, 0);
> - if (stdout_irq == NO_IRQ) {
> + if (!stdout_irq) {
> pr_err("ehv-bc: no 'interrupts' property in %pOF node\n", np);
> return 0;
> }
> @@ -696,7 +696,7 @@ static int ehv_bc_tty_probe(struct platform_device *pdev)
>
> bc->rx_irq = irq_of_parse_and_map(np, 0);
> bc->tx_irq = irq_of_parse_and_map(np, 1);
> - if ((bc->rx_irq == NO_IRQ) || (bc->tx_irq == NO_IRQ)) {
> + if (!bc->rx_irq || !bc->tx_irq) {
> dev_err(&pdev->dev, "no 'interrupts' property in %pOFn node\n",
> np);
> ret = -ENODEV;
--
js
suse labs
next prev parent reply other threads:[~2022-10-06 5:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 5:20 Christophe Leroy
2022-10-06 5:26 ` Jiri Slaby [this message]
2022-10-06 7:35 ` Laurentiu Tudor
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=ec9d6f4e-08fc-1518-3c72-6e5a24c11204@kernel.org \
--to=jirislaby@kernel.org \
--cc=christophe.leroy@csgroup.eu \
--cc=gregkh@linuxfoundation.org \
--cc=laurentiu.tudor@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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
all inboxes | Powered by JetHome®