linux-kernel - Re: [PATCH v4 0/6] staging: vt6655: a series of checkpatch fixes on the file: rxtx.c

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: <64d0f316-3e72-877d-0f6b-3db1d67877ac@gmail.com>
Date:   Mon, 24 Oct 2022 20:09:34 +0200
From:   Philipp Hortmann <philipp.g.hortmann@...il.com>
To:     Tanjuate Brunostar <tanjubrunostar0@...il.com>,
        gregkh@...uxfoundation.org
Cc:     linux-staging@...ts.linux.dev, linux-kernel@...r.kernel.org,
        outreachy@...ts.linux.dev
Subject: Re: [PATCH v4 0/6] staging: vt6655: a series of checkpatch fixes on
 the file: rxtx.c

On 10/24/22 12:01, Tanjuate Brunostar wrote:
> The fixes are similar, mostly long lines splitting. I had to make
> serveral patches to ease the work of inspectors
> 
> v2: fixed a compilation error found by the kernel test robot and
> recompiled the code
> 
> v3: tends out the error persisted in the second version. this version is
> a correction of that
> 
> v4: did some corrections as recommended by Greg KH
> 
> Tanjuate Brunostar (6):
>    staging: vt6655: fix lines ending in a '('
>    staging: vt6655: refactor long lines of code in s_uGetRTSCTSDuration
>    staging: vt6655: refactor long lines of code in s_uFillDataHead
>    staging: vt6655: refactor long lines of code in s_vGenerateTxParamete
>    staging: vt6655: refactor long lines of code in the rest of the file
>    staging: vt6655: refactor code to avoid a line ending in '('
> 
>   drivers/staging/vt6655/rxtx.c | 542 ++++++++++++++++++++--------------
>   1 file changed, 324 insertions(+), 218 deletions(-)
> 


Tested-by: Philipp Hortmann <philipp.g.hortmann@...il.com>