linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shane Huang <shane.huang-5C7GfCeVMHo@public.gmane.org>
To: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Carl Peng <carl.peng-5C7GfCeVMHo@public.gmane.org>,
	Shane Huang <shane.huang-5C7GfCeVMHo@public.gmane.org>
Subject: [PATCH 2/2] i2c-piix4: Use different message for AMD Auxiliary SMBus Controller
Date: Wed, 22 Jan 2014 14:06:52 -0800	[thread overview]
Message-ID: <1390428412-2269-1-git-send-email-shane.huang@amd.com> (raw)

Same messages for AMD main and auxiliary SMBus controllers lead to confusion,
this patch is to remove confusion and keep consistent with non-AMD products.

Signed-off-by: Shane Huang <shane.huang-5C7GfCeVMHo@public.gmane.org>
---
 drivers/i2c/busses/i2c-piix4.c |    3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/drivers/i2c/busses/i2c-piix4.c b/drivers/i2c/busses/i2c-piix4.c
index f71b4d3..d82b8ab 100644
--- a/drivers/i2c/busses/i2c-piix4.c
+++ b/drivers/i2c/busses/i2c-piix4.c
@@ -295,7 +295,8 @@ static int piix4_setup_sb800(struct pci_dev *PIIX4_dev,
 	/* Aux SMBus does not support IRQ information */
 	if (aux) {
 		dev_info(&PIIX4_dev->dev,
-			 "SMBus Host Controller at 0x%x\n", piix4_smba);
+			 "Auxiliary SMBus Host Controller at 0x%x\n",
+			 piix4_smba);
 		return piix4_smba;
 	}
 
-- 
1.7.9.5

             reply	other threads:[~2014-01-22 22:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-22 22:06 Shane Huang [this message]
     [not found] ` <1390428412-2269-1-git-send-email-shane.huang-5C7GfCeVMHo@public.gmane.org>
2014-01-23 12:43   ` [PATCH 2/2] i2c-piix4: Use different message for AMD Auxiliary SMBus Controller Jean Delvare
2014-01-24 16:48   ` Wolfram Sang

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=1390428412-2269-1-git-send-email-shane.huang@amd.com \
    --to=shane.huang-5c7gfcevmho@public.gmane.org \
    --cc=carl.peng-5C7GfCeVMHo@public.gmane.org \
    --cc=khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.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;
as well as URLs for NNTP newsgroup(s).