From: tianyu.lan@intel.com
To: rjw@sisk.pl, lenb@kernel.org, bhelgaas@google.com
Cc: Lan Tianyu <tianyu.lan@intel.com>,
linux-acpi@vger.kernel.org, linux-pci@vger.kernel.org,
stern@rowland.harvard.edu
Subject: [PATCH] PCI/ACPI: Change dev_info() to dev_dbg() in the acpi_pci_set_power_state()
Date: Tue, 30 Jul 2013 10:32:30 +0800 [thread overview]
Message-ID: <1375151550-28632-1-git-send-email-tianyu.lan@intel.com> (raw)
From: Lan Tianyu <tianyu.lan@intel.com>
acpi_pci_set_power_state() produces log of device power state changing.
Now the log is produced by dev_info(). This seems make no sense when user
doesn't open debug option. So change it to dev_dbg() and prevent kernel
log from being.
Reference: https://bugzilla.kernel.org/show_bug.cgi?id=60636
Suggested-by: Alan Stern <stern@rowland.harvard.edu>
Signed-off-by: Lan Tianyu <tianyu.lan@intel.com>
---
drivers/pci/pci-acpi.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/pci/pci-acpi.c b/drivers/pci/pci-acpi.c
index c78cc43..fb3522957 100644
--- a/drivers/pci/pci-acpi.c
+++ b/drivers/pci/pci-acpi.c
@@ -210,7 +210,7 @@ static int acpi_pci_set_power_state(struct pci_dev *dev, pci_power_t state)
}
if (!error)
- dev_info(&dev->dev, "power state changed by ACPI to %s\n",
+ dev_dbg(&dev->dev, "power state changed by ACPI to %s\n",
acpi_power_state_string(state_conv[state]));
return error;
--
1.8.3.2
next reply other threads:[~2013-07-30 2:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-30 2:32 tianyu.lan [this message]
2013-07-30 13:59 ` [PATCH] PCI/ACPI: Change dev_info() to dev_dbg() in the acpi_pci_set_power_state() Rafael J. Wysocki
2013-07-30 15:40 ` Bjorn Helgaas
2013-07-30 23:31 ` Rafael J. Wysocki
2013-07-31 17:26 ` Bjorn Helgaas
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=1375151550-28632-1-git-send-email-tianyu.lan@intel.com \
--to=tianyu.lan@intel.com \
--cc=bhelgaas@google.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=stern@rowland.harvard.edu \
/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;
as well as URLs for NNTP newsgroup(s).