public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nenghua Cao <nhcao@marvell.com>
To: Mark Brown <broonie@kernel.org>
Cc: Liam Girdwood <liam.r.girdwood@linux.intel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] asoc: soc-core: fix coccinelle warnings
Date: Mon, 24 Feb 2014 11:05:14 +0800	[thread overview]
Message-ID: <530AB6EA.7090807@marvell.com> (raw)
In-Reply-To: <20140222025204.GM25940@sirena.org.uk>

On 02/22/2014 10:52 AM, Mark Brown wrote:
> On Fri, Feb 21, 2014 at 04:06:10PM +0800, Nenghua Cao wrote:
> 
>> --- a/sound/soc/soc-core.c
>> +++ b/sound/soc/soc-core.c
>> @@ -2413,7 +2413,7 @@ struct snd_kcontrol *snd_soc_cnew(const struct snd_kcontrol_new *_template,
>>  	struct snd_kcontrol *kcontrol;
>>  	char *name = NULL;
>>  
>> -	memcpy(&template, _template, sizeof(template));
>> +	memcpy(&template, _template, sizeof(struct snd_kcontrol_new));
>>  	template.index = 0;
>>  
>>  	if (!long_name)
> 
> This looks like a regression - it's better form to use the object name
> rather than the type of the object since this prevents errors if the
> type changes.  What coccinelle was suggesting here was to replace with a
> simple assingment statement rather than change the argument within the
> memcpy(), I think this stops the warning showing because of that issue
> since it makes it harder for coccinelle to figure out that this is a
> memcpy() of the whole object.
> 
Hi, Mark

      I am not familiar with coccinelle. But it isn't reasonable and
convenient to use simple assignment instead of memcpy() here. So let's
retain it. I will submit another patch to fix "Assignment of bool to
0/1" issue. How do you think about it?

  reply	other threads:[~2014-02-24  3:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-21  8:06 [PATCH 2/2] asoc: soc-core: fix coccinelle warnings Nenghua Cao
2014-02-22  2:52 ` Mark Brown
2014-02-24  3:05   ` Nenghua Cao [this message]
2014-02-24  5:40     ` 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=530AB6EA.7090807@marvell.com \
    --to=nhcao@marvell.com \
    --cc=broonie@kernel.org \
    --cc=liam.r.girdwood@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    /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