linux-kernel - [PATCH] Remove Spurious PnP Memory Reserved Warning

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1248505976-4952-1-BlackWidow-davidjon@xenontk.org>
Date:	Sat, 25 Jul 2009 12:42:56 +0530
From:	David John <davidjon@...ontk.org>
To:	torvalds@...ux-foundation.org
Cc:	elendil@...net.nl, linux-kernel@...r.kernel.org,
	yinghai@...nel.org, jbarnes@...tuousgeek.org
Subject: [PATCH] Remove Spurious PnP Memory Reserved Warning

An alternate version that ignores just the errors.

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

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

diff --git a/drivers/pnp/system.c b/drivers/pnp/system.c
index 59b9092..84ee297 100644
--- a/drivers/pnp/system.c
+++ b/drivers/pnp/system.c
@@ -48,10 +48,11 @@ 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");
+	if(res) {
+		dev_info(&dev->dev, "%s range 0x%llx-0x%llx has been reserved\n",
+			port ? "ioport" : "iomem",
+			(unsigned long long) start, (unsigned long long) end);
+	}
 }
 
 static void reserve_resources_of_dev(struct pnp_dev *dev)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/