linux-kernel - Re: [PATCH] drm/amd/pm: Clean up errors in smu73

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]

Message-ID: <ZMjposYeMFxU5nE9@debian.me>
Date:   Tue, 1 Aug 2023 18:16:50 +0700
From:   Bagas Sanjaya <bagasdotme@...il.com>
To:     Ran Sun <sunran001@...suo.com>, alexander.deucher@....com,
        airlied@...il.com, daniel@...ll.ch
Cc:     dri-devel@...ts.freedesktop.org, amd-gfx@...ts.freedesktop.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] drm/amd/pm: Clean up errors in smu73_discrete.h

On Tue, Aug 01, 2023 at 10:00:24AM +0000, Ran Sun wrote:
> Fix the following errors reported by checkpatch:
> 
> ERROR: open brace '{' following struct go on the same line
> ERROR: trailing whitespace
> ERROR: space prohibited before open square bracket '['
> 

Thanks for fixing up your tooling to use git-send-email(1). However, it'd
been great to send a patch series touching whole drm/amd subsystem, with each
patch fixes one error (assuming the subsystem permits checkpatch fixup
like this) instead of spamming maintainers with >= 70 single patches like
this.

And it is unfortunate that you and @208suo.com people doesn't reply to
review comments (try searching lore.kernel.org), which makes me wonder:
what does prevent you from replying to the mailing lists like LKML? Your
mail infrastructure?

Thanks anyway.

-- 
An old man doll... just what I always wanted! - Clara

Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)