From: Guenter Roeck <linux@roeck-us.net>
To: Nicholas Krause <xerofoify@gmail.com>, geert@linux-m68k.org
Cc: linux-m68k@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] m68k: Remove printk statement and add return statement in q40ints.c
Date: Tue, 22 Jul 2014 21:54:19 -0700 [thread overview]
Message-ID: <53CF3FFB.4080809@roeck-us.net> (raw)
In-Reply-To: <1406088515-4026-1-git-send-email-xerofoify@gmail.com>
On 07/22/2014 09:08 PM, Nicholas Krause wrote:
> This removes the printk statement for irqs not defined by the hardware in
> function q40_irq_startup and instead returns -ENXIO as stated by the fix
> me message.
>
> Signed-off-by: Nicholas Krause <xerofoify@gmail.com>
> ---
> arch/m68k/q40/q40ints.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/arch/m68k/q40/q40ints.c b/arch/m68k/q40/q40ints.c
> index 513f9bb..86f05c0 100644
> --- a/arch/m68k/q40/q40ints.c
> +++ b/arch/m68k/q40/q40ints.c
> @@ -48,8 +48,7 @@ static unsigned int q40_irq_startup(struct irq_data *data)
> switch (irq) {
> case 1: case 2: case 8: case 9:
> case 11: case 12: case 13:
> - printk("%s: ISA IRQ %d not implemented by HW\n", __func__, irq);
> - /* FIXME return -ENXIO; */
> + return -ENXIO;
Returning -ENXIO from a function returning an unsigned int isn't really very helpful,
don't you think ?
With all those FIXMEs, you might want to keep in mind that there is typically a
good reason for it. If it was as easy as your proposed fix, you can assume
that the FIXME would not have been there in the first place.
Guenter
next prev parent reply other threads:[~2014-07-23 4:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-23 4:08 [PATCH] m68k: Remove printk statement and add return statement in q40ints.c Nicholas Krause
2014-07-23 4:54 ` Guenter Roeck [this message]
2014-07-23 4:56 ` Nick Krause
2014-07-23 5:42 ` Guenter Roeck
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=53CF3FFB.4080809@roeck-us.net \
--to=linux@roeck-us.net \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=xerofoify@gmail.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