From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: Linux Kernel Development <linux-kernel@vger.kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.org>
Subject: [PATCH] M68k invalid vs. illegal
Date: Fri, 29 Aug 2003 16:51:07 +0200 [thread overview]
Message-ID: <200308291451.h7TEp7BC005902@callisto.of.borg> (raw)
M68k: Use `invalid' instead of `illegal' (from Steven Cole in 2.5.x)
--- linux-2.4.23-pre1/arch/m68k/apollo/dn_ints.c Tue Jun 4 15:23:04 2002
+++ linux-m68k-2.4.23-pre1/arch/m68k/apollo/dn_ints.c Mon Jul 21 20:39:55 2003
@@ -43,7 +43,7 @@
int dn_request_irq(unsigned int irq, void (*handler)(int, void *, struct pt_regs *), unsigned long flags, const char *devname, void *dev_id) {
if((irq<0) || (irq>15)) {
- printk("Trying to request illegal IRQ\n");
+ printk("Trying to request invalid IRQ\n");
return -ENXIO;
}
@@ -69,7 +69,7 @@
void dn_free_irq(unsigned int irq, void *dev_id) {
if((irq<0) || (irq>15)) {
- printk("Trying to free illegal IRQ\n");
+ printk("Trying to free invalid IRQ\n");
return ;
}
--- linux-2.4.23-pre1/arch/m68k/q40/q40ints.c Thu Mar 13 07:43:37 2003
+++ linux-m68k-2.4.23-pre1/arch/m68k/q40/q40ints.c Mon Jul 21 20:39:55 2003
@@ -168,7 +168,7 @@
{
case 1: case 2: case 8: case 9:
case 12: case 13:
- printk("%s: ISA IRQ %d from %x illegal\n", __FUNCTION__, irq, (unsigned)dev_id);
+ printk("%s: ISA IRQ %d from %x invalid\n", __FUNCTION__, irq, (unsigned)dev_id);
return;
case 11: irq=10;
default:
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next reply other threads:[~2003-08-29 14:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-29 14:51 Geert Uytterhoeven [this message]
2003-08-29 15:17 ` [PATCH] M68k invalid vs. illegal Steven Cole
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=200308291451.h7TEp7BC005902@callisto.of.borg \
--to=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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).