Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Patrick Waterlander <patrick.waterlander@intel.com>,
	patch@alsa-project.org
Cc: alsa-devel@alsa-project.org, "Kaczmarski,
	Filip" <filip.kaczmarski@intel.com>
Subject: Re: [PATCH 1/1] ASoC: Intel: Skylake: change list empty check to warning
Date: Mon, 29 Apr 2019 08:05:22 -0500	[thread overview]
Message-ID: <e7db2293-dda5-7aa1-f3be-8a9cdf707847@linux.intel.com> (raw)
In-Reply-To: <20190425215743.88673-1-patrick.waterlander@intel.com>

On 4/25/19 4:57 PM, Patrick Waterlander wrote:
> NULL is a valid state for the module list when querying unique ID.
> Downgrade the empty condition from error to warning.
> 
> Signed-off-by: Patrick Waterlander <patrick.waterlander@intel.com>
> 
> diff --git a/sound/soc/intel/skylake/skl-sst.c b/sound/soc/intel/skylake/skl-sst.c
> index 5951bbdf1f1a..95e6a23538cd 100644
> --- a/sound/soc/intel/skylake/skl-sst.c
> +++ b/sound/soc/intel/skylake/skl-sst.c
> @@ -324,7 +324,7 @@ static struct skl_module_table *skl_module_get_from_id(
>   	struct skl_module_table *module;
>   
>   	if (list_empty(&ctx->module_list)) {
> -		dev_err(ctx->dev, "Module list is empty\n");
> +		dev_warn(ctx->dev, "Module list is empty\n");

Not sure what you are trying to fix here? Either it's an error and we 
can keep the message as is or it's not and that trace should go away. 
Changing the level doesn't really add much value, does it?

You should run this by Filip's team (CC:ed) and copy maintainers.

>   		return NULL;
>   	}
>   
> 

      reply	other threads:[~2019-04-29 13:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-25 21:57 [PATCH 1/1] ASoC: Intel: Skylake: change list empty check to warning Patrick Waterlander
2019-04-29 13:05 ` Pierre-Louis Bossart [this message]

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=e7db2293-dda5-7aa1-f3be-8a9cdf707847@linux.intel.com \
    --to=pierre-louis.bossart@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=filip.kaczmarski@intel.com \
    --cc=patch@alsa-project.org \
    --cc=patrick.waterlander@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