From: Alberto Merciai <alb3rt0.m3rciai@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: devel@driverdev.osuosl.org, forest@alittletooquiet.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] staging: vt6655: refactor camelcase uCurrRSSI to current_rssi
Date: Fri, 19 Nov 2021 14:36:44 +0100 [thread overview]
Message-ID: <20211119133644.GB2519@alb3rt0-VirtualBox> (raw)
In-Reply-To: <YZdGaAVSVM8/4ZB2@kroah.com>
driver-core$ ./scripts/get_maintainer.pl drivers/staging/vt6655/device.h
Forest Bond <forest@alittletooquiet.net> (odd fixer:STAGING - VIA VT665X DRIVERS)
Greg Kroah-Hartman <gregkh@linuxfoundation.org> (supporter:STAGING SUBSYSTEM)
Alberto Merciai <alb3rt0.m3rciai@gmail.com> (commit_signer:2/2=100%,authored:2/2=100%,added_lines:2/2=100%,removed_lines:2/2=100%)
devel@driverdev.osuosl.org (open list:STAGING SUBSYSTEM)
linux-kernel@vger.kernel.org (open list)
Regards,
Alberto
On Fri, Nov 19, 2021 at 07:38:32AM +0100, Greg KH wrote:
> On Thu, Nov 18, 2021 at 09:27:18PM +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@gmail.com>
> > ---
> >
> > v2
> > - correct mailing list
>
> No, you did not use the correct mailing list.
>
> What is the output of scripts/get_maintainer.pl on your patch?
>
> thanks,
>
> greg k-h
next prev parent reply other threads:[~2021-11-19 13:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-18 20:27 [PATCH v3] staging: vt6655: refactor camelcase uCurrRSSI to current_rssi Alberto Merciai
2021-11-19 6:38 ` Greg KH
2021-11-19 13:36 ` Alberto Merciai [this message]
2021-11-19 14:17 ` Greg KH
2021-11-19 8:51 ` Dan Carpenter
2021-11-19 12:23 ` Alberto Merciai
2021-11-19 12:29 ` Greg KH
2021-11-19 18:51 ` Your Name
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20211119133644.GB2519@alb3rt0-VirtualBox \
--to=alb3rt0.m3rciai@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=forest@alittletooquiet.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.