linux-kernel - Re: [PATCH] staging: gdm724x: Rename variable for consistency

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-next>] [day] [month] [year] [list]

Date:   Thu, 31 Aug 2017 12:47:59 -0400
From:   Nick Fox <fox.nicholas.j@...il.com>
To:     Greg KH <gregkh@...uxfoundation.org>
Cc:     devel@...verdev.osuosl.org, deanahn@...semi.com,
        jonathankim@...semi.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] staging: gdm724x: Rename variable for consistency

jonathankim@...semi.com, linux-kernel@...r.kernel.org
Bcc: 
Subject: Re: [PATCH v2] staging : gdm724x: Rename variable for consistency
Reply-To: 
In-Reply-To: <20170831162747.GA31171@...ah.com>

Sorry for the confusion. This patch is a revision to an earlier patch I
submitted that did not compile. It should be part of this thread, but in case its not,
reference is here: https://lkml.org/lkml/2017/8/24/885. I thought I had compiled it successfully but I discovered this was due to an issue with my build environment.

Just for future reference, was I doing something wrong in this situation
by adding a v2 in the changelog area? Various beginner guides I've been
reading suggested I do this when a patch requires revisions.

Thanks,
Nick