From: Takashi Iwai <tiwai@suse.de>
To: Yang Li <yang.lee@linux.alibaba.com>
Cc: perex@perex.cz, tiwai@suse.com, alsa-devel@alsa-project.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ALSA: seq: oss: Fix inconsistent indenting
Date: Fri, 16 Apr 2021 12:41:57 +0200 [thread overview]
Message-ID: <s5hlf9iqznu.wl-tiwai@suse.de> (raw)
In-Reply-To: <1618567244-5704-1-git-send-email-yang.lee@linux.alibaba.com>
On Fri, 16 Apr 2021 12:00:44 +0200,
Yang Li wrote:
>
> Kernel test robot throws below warning ->
>
> smatch warnings:
> sound/core/seq/oss/seq_oss_event.c:297 note_on_event() warn:
> inconsistent indenting
>
> Fixed the inconsistent indenting.
>
> Reported-by: Abaci Robot <abaci@linux.alibaba.com>
> Signed-off-by: Yang Li <yang.lee@linux.alibaba.com>
> ---
> sound/core/seq/oss/seq_oss_event.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/sound/core/seq/oss/seq_oss_event.c b/sound/core/seq/oss/seq_oss_event.c
> index 7b7c925..9a42713 100644
> --- a/sound/core/seq/oss/seq_oss_event.c
> +++ b/sound/core/seq/oss/seq_oss_event.c
> @@ -294,7 +294,7 @@
> /* set volume to zero -- note off */
> // type = SNDRV_SEQ_EVENT_NOTEOFF;
> //else
> - if (info->ch[ch].vel)
> + if (info->ch[ch].vel)
> /* sample already started -- volume change */
> type = SNDRV_SEQ_EVENT_KEYPRESS;
The line was aligned with the commented if block.
If any, we should rather clean up and re-format the whole block.
(But, OTOH, you shouldn't remove the stuff without understanding
the context.)
thanks,
Takashi
next prev parent reply other threads:[~2021-04-16 10:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-16 10:00 [PATCH] ALSA: seq: oss: Fix inconsistent indenting Yang Li
2021-04-16 10:41 ` Takashi Iwai [this message]
2021-04-19 10:21 ` 回复:[PATCH] " Yang.Lee
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=s5hlf9iqznu.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
--cc=yang.lee@linux.alibaba.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