From: Ranjani Sridharan <ranjani.sridharan@linux.intel.com>
To: Keyon Jie <yang.jie@linux.intel.com>, alsa-devel@alsa-project.org
Cc: cezary.rojewski@intel.com, tiwai@suse.de,
pierre-louis.bossart@linux.intel.com, broonie@kernel.org,
sathya.prakash.m.r@intel.com, vamshi.krishna.gopal@intel.com
Subject: Re: [PATCH v3 0/2] ASoC topology header parsing refinement
Date: Wed, 27 May 2020 20:40:02 -0700 [thread overview]
Message-ID: <8519ab3772b6abcb3d3458644addfaa5d5dd1fc9.camel@linux.intel.com> (raw)
In-Reply-To: <20200527022801.336264-1-yang.jie@linux.intel.com>
On Wed, 2020-05-27 at 10:27 +0800, Keyon Jie wrote:
> This small series is to optimize the header logging during the
> topology
> parsing. This is verified work fine on both SOF and SST drivers.
>
> Change History:
> v3:
> - Remove using the separated soc_pass_load() function and merge it to
> the
> soc_tplg_load_header() body.
> - Add more Tested-by tags.
>
> v2:
> - Change the internal used array to be 'static' to fix the issue
> reported by: kbuild test robot <lkp@intel.com>
> - Add testing coverage including Intel SST driver also.
>
> v1:
> - Initial version.
>
> Keyon Jie (2):
> ASoC: topology: refine and log the header in the correct pass
> ASoC: topology: remove the redundant pass checks
LGTM, thanks Keyon!
Reviewed-by: Ranjani Sridharan <ranjani.sridharan@linux.intel.com>
next prev parent reply other threads:[~2020-05-28 3:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-27 2:27 [PATCH v3 0/2] ASoC topology header parsing refinement Keyon Jie
2020-05-27 2:28 ` [PATCH v3 1/2] ASoC: topology: refine and log the header in the correct pass Keyon Jie
2020-05-27 2:28 ` [PATCH v3 2/2] ASoC: topology: remove the redundant pass checks Keyon Jie
2020-05-28 3:40 ` Ranjani Sridharan [this message]
2020-05-29 16:51 ` [PATCH v3 0/2] ASoC topology header parsing refinement 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=8519ab3772b6abcb3d3458644addfaa5d5dd1fc9.camel@linux.intel.com \
--to=ranjani.sridharan@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=cezary.rojewski@intel.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=sathya.prakash.m.r@intel.com \
--cc=tiwai@suse.de \
--cc=vamshi.krishna.gopal@intel.com \
--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 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.