All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jarkko Nikula <jarkko.nikula@linux.intel.com>
To: alsa-devel@alsa-project.org
Cc: Oder Chiou <oder_chiou@realtek.com>,
	Bard Liao <bardliao@realtek.com>, Mark Brown <broonie@kernel.org>,
	Jarkko Nikula <jarkko.nikula@linux.intel.com>,
	Liam Girdwood <lgirdwood@gmail.com>
Subject: [PATCH 1/6] ASoC: rt286: Prefix hexadecimal ID register value with 0x in error print
Date: Thu, 25 Jun 2015 13:58:56 +0300	[thread overview]
Message-ID: <1435229941-9574-1-git-send-email-jarkko.nikula@linux.intel.com> (raw)

Make it obvious that unexpected value read from ID register is printed in
hexadecimal.

Signed-off-by: Jarkko Nikula <jarkko.nikula@linux.intel.com>
---
 sound/soc/codecs/rt286.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/sound/soc/codecs/rt286.c b/sound/soc/codecs/rt286.c
index 5c43e263b2c1..2f39843ebd14 100644
--- a/sound/soc/codecs/rt286.c
+++ b/sound/soc/codecs/rt286.c
@@ -1157,7 +1157,7 @@ static int rt286_i2c_probe(struct i2c_client *i2c,
 	}
 	if (val != RT286_VENDOR_ID && val != RT288_VENDOR_ID) {
 		dev_err(&i2c->dev,
-			"Device with ID register %x is not rt286\n", val);
+			"Device with ID register %#x is not rt286\n", val);
 		return -ENODEV;
 	}
 
-- 
2.1.4

             reply	other threads:[~2015-06-25 10:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-25 10:58 Jarkko Nikula [this message]
2015-06-25 10:58 ` [PATCH 2/6] ASoC: rt5640: Prefix hexadecimal ID register value with 0x in error print Jarkko Nikula
2015-07-03 14:10   ` Applied "ASoC: rt5640: Prefix hexadecimal ID register value with 0x in error print" to the asoc tree Mark Brown
2015-06-25 10:58 ` [PATCH 3/6] ASoC: rt5645: Prefix hexadecimal ID register value with 0x in error print Jarkko Nikula
2015-07-03 14:10   ` Applied "ASoC: rt5645: Prefix hexadecimal ID register value with 0x in error print" to the asoc tree Mark Brown
2015-06-25 10:58 ` [PATCH 4/6] ASoC: rt5651: Prefix hexadecimal ID register value with 0x in error print Jarkko Nikula
2015-07-03 14:10   ` Applied "ASoC: rt5651: Prefix hexadecimal ID register value with 0x in error print" to the asoc tree Mark Brown
2015-06-25 10:59 ` [PATCH 5/6] ASoC: rt5670: Prefix hexadecimal ID register value with 0x in error print Jarkko Nikula
2015-07-03 18:10   ` Applied "ASoC: rt5670: Prefix hexadecimal ID register value with 0x in error print" to the asoc tree Mark Brown
2015-06-25 10:59 ` [PATCH 6/6] ASoC: rt5677: Prefix hexadecimal ID register value with 0x in error print Jarkko Nikula
2015-07-03 18:10   ` Applied "ASoC: rt5677: Prefix hexadecimal ID register value with 0x in error print" to the asoc tree Mark Brown
2015-07-03 14:10 ` Applied "ASoC: rt286: " Mark 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=1435229941-9574-1-git-send-email-jarkko.nikula@linux.intel.com \
    --to=jarkko.nikula@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=bardliao@realtek.com \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=oder_chiou@realtek.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.