linux-kernel - Re: [PATCH] ALSA: PCM: Fix codestyle issues in pcm

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 10 May 2023 13:17:59 +0400
From:   Ivan Orlov <ivan.orlov0322@...il.com>
To:     Takashi Iwai <tiwai@...e.de>, perex@...ex.cz, tiwai@...e.com,
        axboe@...nel.dk, 42.hyeyoo@...il.com, surenb@...gle.com,
        alsa-devel@...a-project.org, linux-kernel@...r.kernel.org,
        linux-kernel-mentees@...ts.linuxfoundation.org
Subject: Re: [PATCH] ALSA: PCM: Fix codestyle issues in pcm_native.c

On 10.05.2023 12:21, Oswald Buddenhagen wrote:
> On Wed, May 10, 2023 at 10:06:16AM +0200, Takashi Iwai wrote:
>> Also, if it's only about white space fix or some indent level issues,
>> that could be rather more noise and disturbs the git change history,
>> e.g. it makes difficult to find out the real code changes via git
>> blame, especially it touches a huge amount of lines like this.
>>
>> That said, I'm not going to take such "coding style cleanup" patch
>> blindly.  If it's associated with other real fix or enhancement, I'll
>> happily take it.  Otherwise, I'd rather leave it.
>>
> a maybe less confusing way to put it would be "do whitespace cleanups 
> only on the lines that contain "real" changes, and maybe in their 
> immediate proximity for consistency". that means that whitespace-only 
> patches are by definition not acceptable.
> 
> regards

Oswald, Takashi, thank you for the explanation! I got it. The acceptance 
of codestyle cleanup patches vary from one Kernel area to another. I'm 
curious about the sound subsystem, and decided to fix some obvious 
things before going to more significant enhancements I probably would 
able to make.

Kind regards,
Ivan Orlov.