From: Takashi Iwai <tiwai@suse.de>
To: Edson Juliano Drosdeck <edson.drosdeck@gmail.com>
Cc: tiwai@suse.com, perex@perex.cz, alsa-devel@alsa-project.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ALSA: pci: Missing a blank line after declarations
Date: Tue, 17 Oct 2023 09:45:45 +0200 [thread overview]
Message-ID: <87fs29n13q.wl-tiwai@suse.de> (raw)
In-Reply-To: <20231013015951.16812-1-edson.drosdeck@gmail.com>
On Fri, 13 Oct 2023 03:59:51 +0200,
Edson Juliano Drosdeck wrote:
>
> Warning found by checkpatch.pl script. Adding blank line after declarations.
>
> Signed-off-by: Edson Juliano Drosdeck <edson.drosdeck@gmail.com>
Thanks for the patch. But in general we take such a white-space
cleanup patch only when it's associated with another real code
changes.
Takashi
> ---
> sound/pci/lola/lola_proc.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/sound/pci/lola/lola_proc.c b/sound/pci/lola/lola_proc.c
> index a166672e22cb..1ee5997da3c9 100644
> --- a/sound/pci/lola/lola_proc.c
> +++ b/sound/pci/lola/lola_proc.c
> @@ -137,6 +137,7 @@ static void lola_proc_codec_rw_write(struct snd_info_entry *entry,
> struct lola *chip = entry->private_data;
> char line[64];
> unsigned int id, verb, data, extdata;
> +
> while (!snd_info_get_line(buffer, line, sizeof(line))) {
> if (sscanf(line, "%u %u %u %u", &id, &verb, &data, &extdata) != 4)
> continue;
> @@ -150,6 +151,7 @@ static void lola_proc_codec_rw_read(struct snd_info_entry *entry,
> struct snd_info_buffer *buffer)
> {
> struct lola *chip = entry->private_data;
> +
> snd_iprintf(buffer, "0x%x 0x%x\n", chip->debug_res, chip->debug_res_ex);
> }
>
> --
> 2.39.2
>
prev parent reply other threads:[~2023-10-17 7:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-13 1:59 [PATCH] ALSA: pci: Missing a blank line after declarations Edson Juliano Drosdeck
2023-10-17 7:45 ` 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=87fs29n13q.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=edson.drosdeck@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--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