linux-kernel - Re: [PATCH 0/3] Type encoding info dropped from arrary name "abyBBVGA" and variable names "byBBVGACurrent", "byBBVGANew"

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: <e367844f-7990-0ac9-3898-04cacc863095@gmail.com>
Date:   Sun, 1 Oct 2023 15:53:16 +0200
From:   Philipp Hortmann <philipp.g.hortmann@...il.com>
To:     Pavan Bobba <opensource206@...il.com>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        linux-staging@...ts.linux.dev, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/3] Type encoding info dropped from arrary name
 "abyBBVGA" and variable names "byBBVGACurrent", "byBBVGANew"

On 10/1/23 08:43, Pavan Bobba wrote:
> This patchset series consist of fixes to issues found by checkpatch
> 
> Pavan Bobba (3):
>    staging: vt6655: Type encoding info dropped from array name "abyBBVGA"
>    staging: vt6655: Type encoding info dropped from variable name
>      "byBBVGACurrent"
>    staging: vt6655: Type encoding info dropped from variable name
>      "byBBVGANew"
> 
>   drivers/staging/vt6655/baseband.c    | 40 ++++++++++++++--------------
>   drivers/staging/vt6655/channel.c     |  6 ++---
>   drivers/staging/vt6655/device.h      |  6 ++---
>   drivers/staging/vt6655/device_main.c | 24 ++++++++---------
>   4 files changed, 38 insertions(+), 38 deletions(-)
> 

Hi Pavan,

this is not correct. You need to send all patches as an own email.

It is also required that you include a version history in each patch.

Please have a look at the patches send in.
https://lore.kernel.org/linux-staging/

In the version history your next patch series is V3.
Please document in each patch what has changed.

A sample command I use for this is:
git format-patch -o ~/Documents/kernel/patches/ --subject-prefix="PATCH 
v3" --cover-letter -n --thread=shallow --to="Greg Kroah-Hartman 
<gregkh@...uxfoundation.org>,linux-staging@...ts.linux.dev,linux-kernel@...r.kernel.org" 
f3c8deddac66d11c41ba720e4048aba37e41e885^..HEAD

Thanks for your support.

Bye Philipp