linux-kernel - Re: [PATCH v5] staging: vt6655: refactor camelcase uCurrRSSI to current

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:   Thu, 25 Nov 2021 17:46:00 +0100
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Alberto Merciai <alb3rt0.m3rciai@...il.com>
Cc:     joe@...ches.com, forest@...ttletooquiet.net,
        karolinadrobnik@...il.com, lucas.henneman@...aro.org,
        dan.carpenter@...cle.com, tomm.merciai@...il.com,
        eantoranz@...il.com, linux-kernel@...r.kernel.org,
        linux-staging@...ts.linux.dev
Subject: Re: [PATCH v5] staging: vt6655: refactor camelcase uCurrRSSI to
 current_rssi

On Thu, Nov 18, 2021 at 10:16:59PM +0100, Alberto Merciai wrote:
> Replace camelcase variable "uCurrRSSI" (current Received Signal Strength
> Indicator) into linux kernel coding style equivalent
> variable "current_rssi".
> 
> Signed-off-by: Alberto Merciai <alb3rt0.m3rciai@...il.com>
> ---
> 
> v4
> - rebase against the staging-next

Is this v4 or v5?

Subject says v5, but this says v4 and then you sent v4 two days later?

I'm totally lost, sorry.
Please resend this again and properly set the version number.

thanks,

greg k-h