From: Andrew Morton <akpm@linux-foundation.org>
To: Manuel Quintero Fonseca <sakunix@yahoo.com>
Cc: rafael@kernel.org, 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
Subject: Re: [PATCH v3] resource: Downgrade "resource sanity check" warning to debug level
Date: Fri, 22 May 2026 19:23:58 -0700 [thread overview]
Message-ID: <20260522192358.2a0c2db04578c8281eb22dac@linux-foundation.org> (raw)
In-Reply-To: <20260523000131.7086-1-sakunix@yahoo.com>
On Fri, 22 May 2026 17:01:31 -0700 Manuel Quintero Fonseca <sakunix@yahoo.com> wrote:
> 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.
um, who is "the maintainer"?
hp2:/usr/src/25> grep kernel/resource.c MAINTAINERS
hp2:/usr/src/25>
> This change reduces log clutter while keeping the diagnostic
> information available for debugging purposes if needed.
>
> ...
>
> --- 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;
lgtm, thanks.
next prev parent reply other threads:[~2026-05-23 2:23 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
2026-05-23 2:23 ` Andrew Morton [this message]
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=20260522192358.2a0c2db04578c8281eb22dac@linux-foundation.org \
--to=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=sakunix@yahoo.com \
--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®