From: Toshi Kani <toshi.kani@hp.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: lenb@kernel.org, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org, joe@perches.com,
isimatu.yasuaki@jp.fujitsu.com, liuj97@gmail.com,
srivatsa.bhat@linux.vnet.ibm.com, prarit@redhat.com,
imammedo@redhat.com, vijaymohan.pandarathil@hp.com
Subject: Re: [PATCH v3 4/4] ACPI: Update Container hotplug messages
Date: Thu, 26 Jul 2012 20:52:42 -0600 [thread overview]
Message-ID: <1343357562.3010.533.camel@misato.fc.hp.com> (raw)
In-Reply-To: <CAErSpo4Xqn9b21w1s0BLPwUJ4SeBPQjQOJ=Ar14iQKF1ZWnyHQ@mail.gmail.com>
On Thu, 2012-07-26 at 13:23 -0600, Bjorn Helgaas wrote:
> On Wed, Jul 25, 2012 at 5:12 PM, Toshi Kani <toshi.kani@hp.com> wrote:
> > Updated Container hotplug log messages with acpi_pr_<level>()
> > and pr_<level>().
> >
> > Signed-off-by: Toshi Kani <toshi.kani@hp.com>
> > ---
> > drivers/acpi/container.c | 6 +++---
> > 1 files changed, 3 insertions(+), 3 deletions(-)
> >
> > diff --git a/drivers/acpi/container.c b/drivers/acpi/container.c
> > index 01a986d..643e962 100644
> > --- a/drivers/acpi/container.c
> > +++ b/drivers/acpi/container.c
> > @@ -99,7 +99,7 @@ static int acpi_container_add(struct acpi_device *device)
> >
> >
> > if (!device) {
> > - printk(KERN_ERR PREFIX "device is NULL\n");
> > + pr_err(PREFIX "device is NULL\n");
> > return -EINVAL;
> > }
>
> This whole "if (!device)" check and the printk should be deleted. If
> the ACPI core calls .add() with a null acpi_device pointer, it's a
> core bug, and it's better to take the oops and get the backtrace.
Agreed. Delete the check.
> >
> > @@ -164,7 +164,7 @@ static void container_notify_cb(acpi_handle handle, u32 type, void *context)
> > case ACPI_NOTIFY_BUS_CHECK:
> > /* Fall through */
> > case ACPI_NOTIFY_DEVICE_CHECK:
> > - printk(KERN_WARNING "Container driver received %s event\n",
> > + pr_warn("Container driver received %s event\n",
> > (type == ACPI_NOTIFY_BUS_CHECK) ?
> > "ACPI_NOTIFY_BUS_CHECK" : "ACPI_NOTIFY_DEVICE_CHECK");
>
> This message looks dubious. Receiving this event should be a normal
> occurrence, so the message might be useful for debugging, but doesn't
> seem like a KERN_WARNING event for the user.
Changed to pr_debug() for now.
Thanks!
-Toshi
> >
> > @@ -185,7 +185,7 @@ static void container_notify_cb(acpi_handle handle, u32 type, void *context)
> >
> > result = container_device_add(&device, handle);
> > if (result) {
> > - pr_warn("Failed to add container\n");
> > + acpi_pr_warn(handle, "Failed to add container\n");
> > break;
> > }
> >
> > --
> > 1.7.7.6
> >
next prev parent reply other threads:[~2012-07-27 2:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-25 23:12 [PATCH v3 0/4] ACPI: hotplug messages improvement Toshi Kani
2012-07-25 23:12 ` [PATCH v3 1/4] ACPI: Add acpi_pr_<level>() interfaces Toshi Kani
2012-07-26 19:22 ` Bjorn Helgaas
2012-07-26 20:58 ` Toshi Kani
2012-07-26 21:37 ` Bjorn Helgaas
2012-07-26 21:43 ` Joe Perches
2012-07-26 21:50 ` Bjorn Helgaas
2012-07-26 21:57 ` Joe Perches
2012-07-27 3:32 ` Toshi Kani
2012-07-27 3:27 ` Toshi Kani
2012-07-26 21:50 ` Toshi Kani
2012-07-25 23:12 ` [PATCH v3 2/4] ACPI: Update CPU hotplug messages Toshi Kani
2012-07-26 19:23 ` Bjorn Helgaas
2012-07-27 2:39 ` Toshi Kani
2012-07-27 16:05 ` Bjorn Helgaas
2012-07-27 17:18 ` Toshi Kani
2012-07-25 23:12 ` [PATCH v3 3/4] ACPI: Update Memory " Toshi Kani
2012-07-26 19:23 ` Bjorn Helgaas
2012-07-27 2:50 ` Toshi Kani
2012-07-25 23:12 ` [PATCH v3 4/4] ACPI: Update Container " Toshi Kani
2012-07-26 19:23 ` Bjorn Helgaas
2012-07-27 2:52 ` Toshi Kani [this message]
2012-07-25 23:31 ` [PATCH v3 0/4] ACPI: hotplug messages improvement Joe Perches
2012-07-25 23:34 ` Toshi Kani
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=1343357562.3010.533.camel@misato.fc.hp.com \
--to=toshi.kani@hp.com \
--cc=bhelgaas@google.com \
--cc=imammedo@redhat.com \
--cc=isimatu.yasuaki@jp.fujitsu.com \
--cc=joe@perches.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuj97@gmail.com \
--cc=prarit@redhat.com \
--cc=srivatsa.bhat@linux.vnet.ibm.com \
--cc=vijaymohan.pandarathil@hp.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.