From: Mark Brown <broonie@kernel.org>
To: Defang Bo <bodefang@126.com>
Cc: perex@perex.cz, tiwai@suse.com, lgirdwood@gmail.com,
Vishnuvardhanrao.Ravulapati@amd.com, akshu.agrawal@amd.com,
weiyongjun1@huawei.com, alsa-devel@alsa-project.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] ASoC: amd: move the call to devm_kzalloc below platform_get_resource()
Date: Wed, 21 Oct 2020 10:41:29 +0100 [thread overview]
Message-ID: <20201021094129.GA4497@sirena.org.uk> (raw)
In-Reply-To: <1603263867-8754-1-git-send-email-bodefang@126.com>
[-- Attachment #1: Type: text/plain, Size: 1082 bytes --]
On Wed, Oct 21, 2020 at 03:04:27PM +0800, Defang Bo wrote:
> Just as the commit <4cb79ef9c6c4>("ASoC: amd: Fix potential NULL pointer dereference"),it makes no sense to allocate any resources if platform_get_resource fails,so move the call to devm_kzalloc() below the mentioned code.
As I said on my previous mail:
| Please keep your commit message wrapped at below 80 columns.
Please don't ignore review comments, people are generally making them
for a reason and are likely to have the same concerns if issues remain
unaddressed. Having to repeat the same comments can get repetitive and
make people question the value of time spent reviewing. If you disagree
with the review comments that's fine but you need to reply and discuss
your concerns so that the reviewer can understand your decisions.
> }
> +
> adata = devm_kzalloc(&pdev->dev, sizeof(struct i2s_dev_data), GFP_KERNEL);
> if (!adata)
> return -ENOMEM;
> +
> adata->acp3x_base = devm_ioremap(&pdev->dev, res->start,
This appears to add new whitespace, it doesn't seem to do what the
commit log says?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-10-21 9:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-21 7:04 [PATCH v2] ASoC: amd: move the call to devm_kzalloc below platform_get_resource() Defang Bo
2020-10-21 9:41 ` Mark Brown [this message]
[not found] <broonie@kernel.org>
2020-10-21 7:03 ` Defang Bo
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=20201021094129.GA4497@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Vishnuvardhanrao.Ravulapati@amd.com \
--cc=akshu.agrawal@amd.com \
--cc=alsa-devel@alsa-project.org \
--cc=bodefang@126.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
--cc=weiyongjun1@huawei.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