From: Chase Douglas <chase.douglas@ubuntu.com>
To: linux-acpi@vger.kernel.org
Subject: Re: [PATCH] Reduce ACPI resource conflict message to KERN_INFO, printf cleanup
Date: Wed, 17 Mar 2010 10:15:20 -0400 [thread overview]
Message-ID: <40ec3ea41003170715o250e6457hbc0a0025ea6da3bc@mail.gmail.com> (raw)
In-Reply-To: <1267633294-21815-1-git-send-email-chase.douglas@ubuntu.com>
On Wed, Mar 3, 2010 at 12:21 PM, Chase Douglas <chase.douglas@ubuntu.com> wrote:
> From: Chase Douglas <chase.douglas@canonical.com>
>
> By default, ACPI resource conflict messages are logged at level
> KERN_ERR. This is a rather high level for a message that is more a
> warning than an indication of a real kernel error. Also, KERN_ERR level
> messages can appear over some boot splash screens, and this message is
> not serious enough to warrant such treatment. Thus, the log level has
> been reduced to KERN_INFO.
>
> Also, cleanup message to use %pR resource printing format.
I saw a bunch of patches get rolled into the acpi tree and pulled into
Linus' tree two days ago. I'm not familiar with the process for how
patches are handled in the acpi tree, so when should I expect to see
this patch get pulled in (or NAK'd)?
Thanks,
Chase
next prev parent reply other threads:[~2010-03-17 14:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-03 16:21 [PATCH] Reduce ACPI resource conflict message to KERN_INFO, printf cleanup Chase Douglas
2010-03-17 14:15 ` Chase Douglas [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-03-22 19:08 Chase Douglas
2010-04-05 1:13 ` Len Brown
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=40ec3ea41003170715o250e6457hbc0a0025ea6da3bc@mail.gmail.com \
--to=chase.douglas@ubuntu.com \
--cc=linux-acpi@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