From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Liam Girdwood <liam.r.girdwood@linux.intel.com>,
Jie Yang <yang.jie@linux.intel.com>,
alsa-devel@alsa-project.org, Mark Brown <broonie@kernel.org>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>
Cc: Vinod Koul <vkoul@kernel.org>, Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [PATCH v1] ASoC: Intel: Skylake: Switch to modern UUID API
Date: Wed, 19 Jun 2019 17:46:34 +0200 [thread overview]
Message-ID: <a987bd54-5364-f046-a928-44a97ed0307f@linux.intel.com> (raw)
In-Reply-To: <20190619150213.87691-1-andriy.shevchenko@linux.intel.com>
On 6/19/19 5:02 PM, Andy Shevchenko wrote:
> Switch the driver to use modern UUID API, i.e. guid_t type and
> accompanying functions, such as guid_equal().
>
> Cc: Liam Girdwood <lgirdwood@gmail.com>
> Cc: Mark Brown <broonie@kernel.org>
> Cc: Vinod Koul <vkoul@kernel.org>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Looks good to me - couple of nit-picks below on unrelated indentation
changes.
Reviewed-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
> @@ -247,7 +241,6 @@ int snd_skl_parse_uuids(struct sst_dsp *ctx, const struct firmware *fw,
> struct adsp_fw_hdr *adsp_hdr;
> struct adsp_module_entry *mod_entry;
> int i, num_entry, size;
> - uuid_le *uuid_bin;
> const char *buf;
> struct skl_sst *skl = ctx->thread_context;
> struct uuid_module *module;
> @@ -279,8 +272,7 @@ int snd_skl_parse_uuids(struct sst_dsp *ctx, const struct firmware *fw,
> return -EINVAL;
> }
>
> - mod_entry = (struct adsp_module_entry *)
> - (buf + offset + adsp_hdr->len);
> + mod_entry = (struct adsp_module_entry *)(buf + offset + adsp_hdr->len);
this really has nothing to do with the guid change, could be a separate
patch in a perfect world.
> diff --git a/sound/soc/intel/skylake/skl-sst.c b/sound/soc/intel/skylake/skl-sst.c
> index 5951bbdf1f1a..13c636dece56 100644
> --- a/sound/soc/intel/skylake/skl-sst.c
> +++ b/sound/soc/intel/skylake/skl-sst.c
> @@ -420,11 +420,9 @@ static int skl_load_module(struct sst_dsp *ctx, u16 mod_id, u8 *guid)
> struct skl_module_table *module_entry = NULL;
> int ret = 0;
> char mod_name[64]; /* guid str = 32 chars + 4 hyphens */
> - uuid_le *uuid_mod;
>
> - uuid_mod = (uuid_le *)guid;
> snprintf(mod_name, sizeof(mod_name), "%s%pUL%s",
> - "intel/dsp_fw_", uuid_mod, ".bin");
> + "intel/dsp_fw_", guid, ".bin");
indentation looks off, not sure if this is a diff effect.
next prev parent reply other threads:[~2019-06-19 15:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-19 15:02 [PATCH v1] ASoC: Intel: Skylake: Switch to modern UUID API Andy Shevchenko
2019-06-19 15:46 ` Pierre-Louis Bossart [this message]
2019-06-20 15:09 ` Andy Shevchenko
2019-06-21 3:41 ` Pierre-Louis Bossart
2019-06-24 8:51 ` Amadeusz Sławiński
2019-06-25 17:15 ` Andy Shevchenko
-- strict thread matches above, loose matches on Subject: below --
2018-07-16 9:52 Andy Shevchenko
2019-01-07 15:55 ` Andy Shevchenko
2019-01-07 16:33 ` Pierre-Louis Bossart
2019-01-07 17:24 ` Andy Shevchenko
2019-01-21 8:53 ` Christoph Hellwig
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=a987bd54-5364-f046-a928-44a97ed0307f@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
--cc=vkoul@kernel.org \
--cc=yang.jie@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;
as well as URLs for NNTP newsgroup(s).