linux-kernel - Re: [PATCH v3] 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] [day] [month] [year] [list]

Date:   Fri, 19 Nov 2021 19:51:41 +0100
From:   Your Name <alb3rt0.m3rciai@...il.com>
To:     Greg KH <gregkh@...uxfoundation.org>
Cc:     Dan Carpenter <dan.carpenter@...cle.com>,
        devel@...verdev.osuosl.org, forest@...ttletooquiet.net,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3] staging: vt6655: refactor camelcase uCurrRSSI to
 current_rssi

> What caused you to pick that one?

My mistake :(

I was reading "Submitting patches: the essential guide
to getting your code into the kernel" and I was confuse dby this line
"See the T: entry for the subsystem in the MAINTAINERS file to find 
that tree, or simply ask the maintainer if the tree is not listed
there." supposing that master branch was the correct one.

I'm moving on "staging-next" branch as you suggest.

Regards,

Alberto