From: Mark Brown <broonie@kernel.org>
To: Tuo Li <t-li20@mails.tsinghua.edu.cn>
Cc: alsa-devel@alsa-project.org, heiko@sntech.de,
linux-kernel@vger.kernel.org, tiwai@suse.com,
lgirdwood@gmail.com, linux-rockchip@lists.infradead.org,
baijiaju1990@gmail.com, perex@perex.cz,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ASoC: rockchip: fix a possible divide-by-zero bug in rockchip_i2s_hw_params()
Date: Fri, 25 Sep 2020 20:28:44 +0100 [thread overview]
Message-ID: <20200925192844.GA10127@sirena.org.uk> (raw)
In-Reply-To: <20200830095106.4412-1-t-li20@mails.tsinghua.edu.cn>
[-- Attachment #1.1: Type: text/plain, Size: 659 bytes --]
On Sun, Aug 30, 2020 at 05:51:06PM +0800, Tuo Li wrote:
> The variable bclk_rate is checked in:
> if (bclk_rate && mclk_rate % bclk_rate)
This doesn't apply against current code, please check and resend:
HEAD is now at bbd59df075ab Merge series "ASoC: Intel: sdw machine driver updates for 5.10" from Kai Vehmanen <kai.vehmanen@linux.intel.com>:
Applying: ASoC: rockchip: fix a possible divide-by-zero bug in rockchip_i2s_hw_params()
Using index info to reconstruct a base tree...
M sound/soc/rockchip/rockchip_i2s.c
Falling back to patching base and 3-way merge...
Auto-merging sound/soc/rockchip/rockchip_i2s.c
CONFLICT (content): Merge conflict in sou
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
prev parent reply other threads:[~2020-09-25 19:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-30 9:51 [PATCH] ALSA: rockchip: fix a possible divide-by-zero bug in rockchip_i2s_hw_params() Tuo Li
2020-09-25 16:51 ` Mark Brown
2020-09-25 19:28 ` Mark Brown [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=20200925192844.GA10127@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=baijiaju1990@gmail.com \
--cc=heiko@sntech.de \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=perex@perex.cz \
--cc=t-li20@mails.tsinghua.edu.cn \
--cc=tiwai@suse.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).