mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Manuel Quintero Fonseca <sakunix@yahoo.com>
To: rafael@kernel.org, akpm@linux-foundation.org
Cc: bhelgaas@google.com, linux-acpi@vger.kernel.org,
	linux-kernel@vger.kernel.org, skhan@linuxfoundation.org,
	andriy.shevchenko@linux.intel.com,
	mika.westerberg@linux.intel.com, hansg@kernel.org,
	Manuel Quintero Fonseca <sakunix@yahoo.com>
Subject: [PATCH v3] resource: Downgrade "resource sanity check" warning to debug level
Date: Fri, 22 May 2026 17:01:31 -0700	[thread overview]
Message-ID: <20260523000131.7086-1-sakunix@yahoo.com> (raw)
In-Reply-To: <CAJZ5v0ikd24Vj3H=2XAGwwHtBudDXJumL4H-whu1GgU-KjMnmQ@mail.gmail.com>

The "resource sanity check" warning currently triggers on certain
systems, causing unnecessary noise in the kernel logs for users.
Following the maintainer's suggestion, this patch downgrades the log
level from pr_warn to pr_debug.

This change reduces log clutter while keeping the diagnostic
information available for debugging purposes if needed.

Signed-off-by: Manuel Quintero Fonseca <sakunix@yahoo.com>
---
v3:
   - Downgrade 'resource sanity check' warning to debug level to reduce log 
     noise, as suggested by the maintainer.
   - Drop the previous DMI-based quirk approach as it is no longer needed.

 kernel/resource.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/kernel/resource.c b/kernel/resource.c
index d02a53fb95d8..e676ea99c93c 100644
--- a/kernel/resource.c
+++ b/kernel/resource.c
@@ -1859,7 +1859,7 @@ int iomem_map_sanity_check(resource_size_t addr, unsigned long size)
 		if (p->flags & IORESOURCE_BUSY)
 			continue;
 
-		pr_warn("resource sanity check: requesting [mem %pa-%pa], which spans more than %s %pR\n",
+		pr_debug("resource sanity check: requesting [mem %pa-%pa], which spans more than %s %pR\n",
 			&addr, &end, p->name, p);
 		err = -1;
 		break;
-- 
2.47.3


       reply	other threads:[~2026-05-23  0:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAJZ5v0ikd24Vj3H=2XAGwwHtBudDXJumL4H-whu1GgU-KjMnmQ@mail.gmail.com>
2026-05-23  0:01 ` Manuel Quintero Fonseca [this message]
2026-05-23  2:23   ` Andrew Morton
2026-05-23 17:23   ` Rafael J. Wysocki

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=20260523000131.7086-1-sakunix@yahoo.com \
    --to=sakunix@yahoo.com \
    --cc=akpm@linux-foundation.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=bhelgaas@google.com \
    --cc=hansg@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=rafael@kernel.org \
    --cc=skhan@linuxfoundation.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®