public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 3/4] ACPI: Update Memory hotplug messages
Date: Thu, 26 Jul 2012 20:50:02 -0600	[thread overview]
Message-ID: <1343357402.3010.530.camel@misato.fc.hp.com> (raw)
In-Reply-To: <CAErSpo6Dn8+pOsSuiMDNzwheH=LELRKhkWeSB__S0WjHBz13nA@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 Memory hotplug log messages with acpi_pr_<level>()
> > and pr_<level>().
> >
> > Signed-off-by: Toshi Kani <toshi.kani@hp.com>
> > ---
> >  drivers/acpi/acpi_memhotplug.c |   24 ++++++++++++------------
> >  1 files changed, 12 insertions(+), 12 deletions(-)
> >
> > diff --git a/drivers/acpi/acpi_memhotplug.c b/drivers/acpi/acpi_memhotplug.c
> > index 06c55cd..dcc8f4d 100644
> > --- a/drivers/acpi/acpi_memhotplug.c
> > +++ b/drivers/acpi/acpi_memhotplug.c
> > @@ -170,7 +170,7 @@ acpi_memory_get_device(acpi_handle handle,
> >         /* Get the parent device */
> >         result = acpi_bus_get_device(phandle, &pdevice);
> >         if (result) {
> > -               printk(KERN_WARNING PREFIX "Cannot get acpi bus device");
> > +               acpi_pr_warn(phandle, "Cannot get acpi bus device\n");
> >                 return -EINVAL;
> >         }
> >
> > @@ -180,14 +180,14 @@ acpi_memory_get_device(acpi_handle handle,
> >          */
> >         result = acpi_bus_add(&device, pdevice, handle, ACPI_BUS_TYPE_DEVICE);
> >         if (result) {
> > -               printk(KERN_WARNING PREFIX "Cannot add acpi bus");
> > +               acpi_pr_warn(handle, "Cannot add acpi bus\n");
> >                 return -EINVAL;
> >         }
> >
> >        end:
> >         *mem_device = acpi_driver_data(device);
> >         if (!(*mem_device)) {
> > -               printk(KERN_ERR "\n driver data not found");
> > +               acpi_pr_err(handle, "driver data not found\n");
> 
> acpi_driver_data() requires a valid acpi_device *, so dev_err() should
> work here.

Agreed. Changed to use dev_err().

> 
> >                 return -ENODEV;
> >         }
> >
> > @@ -224,7 +224,7 @@ static int acpi_memory_enable_device(struct acpi_memory_device *mem_device)
> >         /* Get the range from the _CRS */
> >         result = acpi_memory_get_device_resources(mem_device);
> >         if (result) {
> > -               printk(KERN_ERR PREFIX "get_device_resources failed\n");
> > +               pr_err(PREFIX "get_device_resources failed\n");
> 
> And here.

Changed to use dev_err().

> 
> >                 mem_device->state = MEMORY_INVALID_STATE;
> >                 return result;
> >         }
> > @@ -257,7 +257,7 @@ static int acpi_memory_enable_device(struct acpi_memory_device *mem_device)
> >                 num_enabled++;
> >         }
> >         if (!num_enabled) {
> > -               printk(KERN_ERR PREFIX "add_memory failed\n");
> > +               acpi_pr_err(mem_device->device->handle, "add_memory failed\n");
> 
> And here.

Changed to use dev_err().

> 
> >                 mem_device->state = MEMORY_INVALID_STATE;
> >                 return -EINVAL;
> >         }
> > @@ -353,7 +353,7 @@ static void acpi_memory_device_notify(acpi_handle handle, u32 event, void *data)
> >                         ACPI_DEBUG_PRINT((ACPI_DB_INFO,
> >                                           "\nReceived DEVICE CHECK notification for device\n"));
> >                 if (acpi_memory_get_device(handle, &mem_device)) {
> > -                       printk(KERN_ERR PREFIX "Cannot find driver data\n");
> > +                       acpi_pr_err(handle, "Cannot find driver data\n");
> >                         break;
> >                 }
> >
> > @@ -361,7 +361,7 @@ static void acpi_memory_device_notify(acpi_handle handle, u32 event, void *data)
> >                         break;
> >
> >                 if (acpi_memory_enable_device(mem_device)) {
> > -                       pr_err(PREFIX "Cannot enable memory device\n");
> > +                       acpi_pr_err(handle, "Cannot enable memory device\n");
> 
> And here.

No change since it is called directly from the handler.

> >                         break;
> >                 }
> >
> > @@ -373,12 +373,12 @@ static void acpi_memory_device_notify(acpi_handle handle, u32 event, void *data)
> >                                   "\nReceived EJECT REQUEST notification for device\n"));
> >
> >                 if (acpi_bus_get_device(handle, &device)) {
> > -                       printk(KERN_ERR PREFIX "Device doesn't exist\n");
> > +                       acpi_pr_err(handle, "Device doesn't exist\n");
> >                         break;
> >                 }
> >                 mem_device = acpi_driver_data(device);
> >                 if (!mem_device) {
> > -                       printk(KERN_ERR PREFIX "Driver Data is NULL\n");
> > +                       acpi_pr_err(handle, "Driver Data is NULL\n");
> 
> And here.

No change since it is called directly from the handler.

> >                         break;
> >                 }
> >
> > @@ -389,7 +389,7 @@ static void acpi_memory_device_notify(acpi_handle handle, u32 event, void *data)
> >                  *      with generic sysfs driver
> >                  */
> >                 if (acpi_memory_disable_device(mem_device)) {
> > -                       pr_err(PREFIX "Disable memory device\n");
> > +                       acpi_pr_err(handle, "Disable memory device\n");
> 
> And here.  (What is this message supposed to mean, anyway?)

I changed the message to "Failed to remove memory device\n". This case
is failed in off-lining or ejecting the memory.

> >                         /*
> >                          * If _EJ0 was called but failed, _OST is not
> >                          * necessary.
> > @@ -449,7 +449,7 @@ static int acpi_memory_device_add(struct acpi_device *device)
> >         /* Set the device state */
> >         mem_device->state = MEMORY_POWER_ON_STATE;
> >
> > -       printk(KERN_DEBUG "%s \n", acpi_device_name(device));
> > +       pr_debug("%s\n", acpi_device_name(device));
> 
> And here.  This message looks dubious anyway.

It kept it as is since it is a debug message anyway. I expect it will be
removed eventually.

> >
> >         /*
> >          * Early boot code has recognized memory area by EFI/E820.
> > @@ -464,7 +464,7 @@ static int acpi_memory_device_add(struct acpi_device *device)
> >                 /* call add_memory func */
> >                 result = acpi_memory_enable_device(mem_device);
> >                 if (result)
> > -                       printk(KERN_ERR PREFIX
> > +                       acpi_pr_err(device->handle,
> >                                 "Error in acpi_memory_enable_device\n");
> 
> And here.

Changed to use dev_err().


Thanks!
-Toshi


> 
> >         }
> >         return result;
> > --
> > 1.7.7.6
> >



  reply	other threads:[~2012-07-27  2:54 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 [this message]
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
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=1343357402.3010.530.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox