Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Jarkko Nikula <jarkko.nikula@linux.intel.com>,
	Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org
Subject: Applied "ASoC: rt5640: Prefix hexadecimal ID register value with 0x in error print" to the asoc tree
Date: Fri, 03 Jul 2015 15:10:44 +0100	[thread overview]
Message-ID: <E1ZB1fw-00024i-Ut@finisterre> (raw)
In-Reply-To: <1435229941-9574-2-git-send-email-jarkko.nikula@linux.intel.com>

The patch

   ASoC: rt5640: Prefix hexadecimal ID register value with 0x in error print

has been applied to the asoc tree at

   git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git 

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.  

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark

>From 1ef422dc74a1ef4e1970a634899a573196c0a2fb Mon Sep 17 00:00:00 2001
From: Jarkko Nikula <jarkko.nikula@linux.intel.com>
Date: Thu, 25 Jun 2015 13:58:57 +0300
Subject: [PATCH] ASoC: rt5640: Prefix hexadecimal ID register value with 0x in
 error print

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

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

diff --git a/sound/soc/codecs/rt5640.c b/sound/soc/codecs/rt5640.c
index f40752a..67ae249 100644
--- a/sound/soc/codecs/rt5640.c
+++ b/sound/soc/codecs/rt5640.c
@@ -2208,7 +2208,7 @@ static int rt5640_i2c_probe(struct i2c_client *i2c,
 	regmap_read(rt5640->regmap, RT5640_VENDOR_ID2, &val);
 	if (val != RT5640_DEVICE_ID) {
 		dev_err(&i2c->dev,
-			"Device with ID register %x is not rt5640/39\n", val);
+			"Device with ID register %#x is not rt5640/39\n", val);
 		return -ENODEV;
 	}
 
-- 
2.1.4

  reply	other threads:[~2015-07-03 14:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-25 10:58 [PATCH 1/6] ASoC: rt286: Prefix hexadecimal ID register value with 0x in error print Jarkko Nikula
2015-06-25 10:58 ` [PATCH 2/6] ASoC: rt5640: " Jarkko Nikula
2015-07-03 14:10   ` Mark Brown [this message]
2015-06-25 10:58 ` [PATCH 3/6] ASoC: rt5645: " 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=E1ZB1fw-00024i-Ut@finisterre \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=jarkko.nikula@linux.intel.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