mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: [PATCH] quiet IDE resource reservation messages
Date: Sat, 17 Dec 2005 09:30:24 -0800	[thread overview]
Message-ID: <200512170930.24218.jbarnes@virtuousgeek.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 296 bytes --]

In combined mode, having IDE resources reserved before the IDE driver 
can get to them is normal and expected, so quiet the 'resource 
conflict' messages a bit so as not to alarm anyone (and clean up my 
'quiet' boot a bit).

Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>

Thanks,
Jesse

[-- Attachment #2: ide-silence-info.patch --]
[-- Type: text/x-diff, Size: 895 bytes --]

diff --git a/drivers/ide/ide-probe.c b/drivers/ide/ide-probe.c
index 02167a5..57325a2 100644
--- a/drivers/ide/ide-probe.c
+++ b/drivers/ide/ide-probe.c
@@ -773,7 +773,7 @@ static void probe_hwif(ide_hwif_t *hwif)
 			}
 		}
 		if (!msgout)
-			printk(KERN_ERR "%s: ports already in use, skipping probe\n",
+			printk(KERN_INFO "%s: ports already in use, skipping probe\n",
 				hwif->name);
 		return;	
 	}
diff --git a/drivers/ide/ide.c b/drivers/ide/ide.c
index 8af179b..84dd69b 100644
--- a/drivers/ide/ide.c
+++ b/drivers/ide/ide.c
@@ -366,8 +366,8 @@ static struct resource* hwif_request_reg
 	struct resource *res = request_region(addr, num, hwif->name);
 
 	if (!res)
-		printk(KERN_ERR "%s: I/O resource 0x%lX-0x%lX not free.\n",
-				hwif->name, addr, addr+num-1);
+		printk(KERN_INFO "%s: I/O resource 0x%lX-0x%lX not free.\n",
+				 hwif->name, addr, addr+num-1);
 	return res;
 }
 

                 reply	other threads:[~2005-12-17 17:30 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200512170930.24218.jbarnes@virtuousgeek.org \
    --to=jbarnes@virtuousgeek.org \
    --cc=bzolnier@gmail.com \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®