From: Cezary Rojewski <cezary.rojewski@intel.com>
To: Peter Ujfalusi <peter.ujfalusi@linux.intel.com>,
<lgirdwood@gmail.com>, <broonie@kernel.org>,
<pierre-louis.bossart@linux.intel.com>
Cc: alsa-devel@alsa-project.org, yung-chuan.liao@linux.intel.com,
tiwai@suse.com, kai.vehmanen@linux.intel.com
Subject: Re: [PATCH v2 0/2] ASoC: Intel: Skylake: Fixes for skl_get_ssp_clks()
Date: Tue, 5 Jul 2022 15:05:23 +0200 [thread overview]
Message-ID: <2c52f392-c424-31f3-eff6-6eb6124ebeff@intel.com> (raw)
In-Reply-To: <20220630065638.11183-1-peter.ujfalusi@linux.intel.com>
On 2022-06-30 8:56 AM, Peter Ujfalusi wrote:
> Hi,
>
> Changes since v1:
> - drop reference to a might never happening patch from the commit message of
> patch 2.
>
> Cover letter:
> while looking at long standing sparse reports regarding to arrays of flexible
> structures (arrays of flexible arrays of flexible structures, really).
>
> I came across these which did not looked right.
> The skl_get_ssp_clks() as some issues and can work under only strict single
> condition.
Thanks for addressing this issue. I reviewed the code and see no
problems with it, so:
Reviewed-by: Cezary Rojewski <cezary.rojewski@intel.com>
Regards,
Czarek
next prev parent reply other threads:[~2022-07-05 13:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 6:56 [PATCH v2 0/2] ASoC: Intel: Skylake: Fixes for skl_get_ssp_clks() Peter Ujfalusi
2022-06-30 6:56 ` [PATCH v2 1/2] ASoC: Intel: Skylake: Correct the ssp rate discovery in skl_get_ssp_clks() Peter Ujfalusi
2022-06-30 6:56 ` [PATCH v2 2/2] ASoC: Intel: Skylake: Correct the handling of fmt_config flexible array Peter Ujfalusi
2022-07-05 13:05 ` Cezary Rojewski [this message]
2022-07-06 10:16 ` [PATCH v2 0/2] ASoC: Intel: Skylake: Fixes for skl_get_ssp_clks() 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=2c52f392-c424-31f3-eff6-6eb6124ebeff@intel.com \
--to=cezary.rojewski@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=kai.vehmanen@linux.intel.com \
--cc=lgirdwood@gmail.com \
--cc=peter.ujfalusi@linux.intel.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=tiwai@suse.com \
--cc=yung-chuan.liao@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