All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Liam Girdwood <liam.r.girdwood@linux.intel.com>
Cc: alsa-devel@alsa-project.org, Mark Brown <broonie@kernel.org>
Subject: Applied "ASoC: topology: rephrase deferred binding warning." to the asoc tree
Date: Wed, 07 Jun 2017 20:31:51 +0100	[thread overview]
Message-ID: <E1dIggJ-0003gJ-8y@debutante> (raw)
In-Reply-To: <1496760309-6195-3-git-send-email-liam.r.girdwood@linux.intel.com>

The patch

   ASoC: topology: rephrase deferred binding warning.

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 cc9d4714a8da98f905c63d74e9897fc6f4563fca Mon Sep 17 00:00:00 2001
From: Liam Girdwood <liam.r.girdwood@linux.intel.com>
Date: Tue, 6 Jun 2017 15:45:08 +0100
Subject: [PATCH] ASoC: topology: rephrase deferred binding warning.

Rewrite the message to be more meaningful.

Signed-off-by: Liam Girdwood <liam.r.girdwood@linux.intel.com>
Signed-off-by: Mark Brown <broonie@kernel.org>
---
 sound/soc/soc-topology.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/sound/soc/soc-topology.c b/sound/soc/soc-topology.c
index 273a374e741c..f24d1f2e82a0 100644
--- a/sound/soc/soc-topology.c
+++ b/sound/soc/soc-topology.c
@@ -1648,7 +1648,7 @@ static int soc_tplg_dapm_complete(struct soc_tplg *tplg)
 	*/
 	if (!card || !card->instantiated) {
 		dev_warn(tplg->dev, "ASoC: Parent card not yet available,"
-				"Do not add new widgets now\n");
+			" widget card binding deferred\n");
 		return 0;
 	}
 
-- 
2.11.0

  reply	other threads:[~2017-06-07 19:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-06 14:45 [PATCH] ASoC: topology: Fix build by declaring snd_kcontrol_new and soc_dai_link Liam Girdwood
2017-06-06 14:45 ` [PATCH] ASoC: topology: Allow bespoke configuration post widget creation Liam Girdwood
2017-06-07 19:31   ` Applied "ASoC: topology: Allow bespoke configuration post widget creation" to the asoc tree Mark Brown
2017-06-06 14:45 ` [PATCH] ASoC: topology: rephrase deferred binding warning Liam Girdwood
2017-06-07 19:31   ` Mark Brown [this message]
2017-06-06 14:45 ` [PATCH] ASoC: topology: Dont free template strings whilst they are in use Liam Girdwood
2017-06-07 19:31   ` Applied "ASoC: topology: Dont free template strings whilst they are in use." to the asoc tree Mark Brown
2017-06-06 14:49 ` [PATCH] ASoC: topology: Fix build by declaring snd_kcontrol_new and soc_dai_link Liam Girdwood

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=E1dIggJ-0003gJ-8y@debutante \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=liam.r.girdwood@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 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.