mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David John <davidjon@xenontk.org>
To: torvalds@linux-foundation.org
Cc: elendil@planet.nl, linux-kernel@vger.kernel.org,
	yinghai@kernel.org, jbarnes@virtuousgeek.org
Subject: [PATCH] Remove Spurious PnP Memory Reserved Warning
Date: Fri, 24 Jul 2009 11:41:23 +0530	[thread overview]
Message-ID: <1248415883-11809-1-git-send-email-davidjon@xenontk.org> (raw)
In-Reply-To: <200907240953.48297.elendil@planet.nl>

>From 645da858c547a6badd231e66003f58f32eb985a2 Mon Sep 17 00:00:00 2001
From: David John <davidjon@xenontk.org>
Date: Fri, 24 Jul 2009 10:36:15 +0530
Subject: [PATCH] Remove Spurious PnP Memory Reserved Warning

I'd rather you just remove it. Kind of like the following.
Apply if you feel it is ok to _not_ print these messages...
(Sorry for the previous mangled one...)

Remove unnecessary complaints about memory ranges being reserved by the
PnP sub-system.

Signed-off-by: David John <davidjon@xenontk.org>

diff --git a/drivers/pnp/system.c b/drivers/pnp/system.c
index 59b9092..feda64e 100644
--- a/drivers/pnp/system.c
+++ b/drivers/pnp/system.c
@@ -48,10 +48,6 @@ static void reserve_range(struct pnp_dev *dev, resource_size_t start,
 	 * example do reserve stuff they know about too, so we may well
 	 * have double reservations.
 	 */
-	dev_info(&dev->dev, "%s range 0x%llx-0x%llx %s reserved\n",
-		port ? "ioport" : "iomem",
-		(unsigned long long) start, (unsigned long long) end,
-		res ? "has been" : "could not be");
 }
 
 static void reserve_resources_of_dev(struct pnp_dev *dev)

  reply	other threads:[~2009-07-24  6:10 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-23  2:44 Linux 2.6.31-rc4 Linus Torvalds
2009-07-23 14:14 ` Linux 2.6.31-rc4: strange change in iomem allocation Frans Pop
2009-07-23 14:42   ` Yinghai Lu
2009-07-23 15:57     ` Jesse Barnes
2009-07-23 14:53   ` Frans Pop
2009-07-23 16:12     ` Linus Torvalds
2009-07-23 16:29       ` Linus Torvalds
2009-07-24  4:34         ` David John
2009-07-24  5:51           ` Kind of like the following. Apply if you feel it is ok to _not_ David John
2009-07-24  7:53       ` [PATCH?] Re: Linux 2.6.31-rc4: strange change in iomem allocation Frans Pop
2009-07-24  6:11         ` David John [this message]
2009-07-25  7:12           ` [PATCH] Remove Spurious PnP Memory Reserved Warning David John
2009-07-28  4:06             ` [PATCH v2] " David John
2009-07-28 16:31               ` Jesse Barnes
2009-07-29  6:42                 ` David John
2009-08-01 10:56                 ` Frans Pop
2009-08-06 21:41                   ` Jesse Barnes
2009-07-23 17:21 ` Linux 2.6.31-rc4 Krzysztof Olędzki

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=1248415883-11809-1-git-send-email-davidjon@xenontk.org \
    --to=davidjon@xenontk.org \
    --cc=elendil@planet.nl \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=yinghai@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®