mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Vincent Heuken <me@vincentheuken.com>
Cc: perex@perex.cz, alsa-devel@alsa-project.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Sound: Core: fixed assignment in if condition style error in hwdep.c
Date: Mon, 23 Jun 2014 18:12:13 +0200	[thread overview]
Message-ID: <s5ha9931u76.wl%tiwai@suse.de> (raw)
In-Reply-To: <1403279435-31231-1-git-send-email-me@vincentheuken.com>

At Fri, 20 Jun 2014 08:50:35 -0700,
Vincent Heuken wrote:
> 
> This is a patch to the hwdep.c file that fixes one instance of
> the following error:
> ERROR: do not use assignment in if condition
> 
> It also, incidentally, fixes one instance of the following warning:
> WARNING: line over 80 characters
> 
> Signed-off-by: Vincent Heuken <me@vincentheuken.com>

If this is a preliminary work for any real fix, I'd happily apply this
patch.  But, if it's only about a coding style fix, I won't buy it
alone.  Let me know if it's the former case.


thanks,

Takashi

> ---
>  sound/core/hwdep.c | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/sound/core/hwdep.c b/sound/core/hwdep.c
> index 69459e5..42d8324 100644
> --- a/sound/core/hwdep.c
> +++ b/sound/core/hwdep.c
> @@ -527,7 +527,9 @@ static void __init snd_hwdep_proc_init(void)
>  {
>  	struct snd_info_entry *entry;
>  
> -	if ((entry = snd_info_create_module_entry(THIS_MODULE, "hwdep", NULL)) != NULL) {
> +	entry = snd_info_create_module_entry(THIS_MODULE, "hwdep", NULL);
> +
> +	if (entry != NULL) {
>  		entry->c.text.read = snd_hwdep_proc_read;
>  		if (snd_info_register(entry) < 0) {
>  			snd_info_free_entry(entry);
> -- 
> 2.0.0
> 

      reply	other threads:[~2014-06-23 16:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-20 15:50 Vincent Heuken
2014-06-23 16:12 ` Takashi Iwai [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=s5ha9931u76.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=me@vincentheuken.com \
    --cc=perex@perex.cz \
    /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

all inboxes | Powered by JetHome®