From: Pavan Bobba <opensource206@gmail.com>
To: Nam Cao <namcaov@gmail.com>
Cc: Forest Bond <forest@alittletooquiet.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Michael Straube <straube.linux@gmail.com>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] staging: vt6655: Type encoding info dropped from array name "byVT3253B0_"
Date: Mon, 11 Sep 2023 18:09:06 +0530 [thread overview]
Message-ID: <ZP8Kakx1sUjnjWrQ@ubuntu.myguest.virtualbox.org> (raw)
In-Reply-To: <ZPxCa/UOd7T2phqX@nam-dell>
On Sat, Sep 09, 2023 at 12:01:15PM +0200, Nam Cao wrote:
> On Sat, Sep 09, 2023 at 02:13:09PM +0530, Pavan Bobba wrote:
> > On Thu, Sep 07, 2023 at 03:43:53PM +0100, Greg KH wrote:
> > > On Thu, Sep 07, 2023 at 06:40:27PM +0530, Pavan Bobba wrote:
> > > > Below array names updated as per coding guidelines:
> > > >
> > > > 1.byVT3253B0_AGC4_RFMD2959
> > > > 2.byVT3253B0_AIROHA2230
> > > > 3.byVT3253B0_UW2451
> > > > 4.byVT3253B0_AGC
> > > >
> > > > Conversions performed:
> > > > a.type encoding info dropped from names
> > > > b.names replaced by snakecase
> > > >
> > > > Issue found by checkpatch
> > > >
> > > > Signed-off-by: Pavan Bobba <opensource206@gmail.com>
> > > > ---
> > > > v1 -> v2: Name of the tool added in the body of explanation,
> > > > which found this issue
> > > >
> > > > v2 -> v3: subject modified to more specific detail
> > >
> > > Any specific reason you are not sending this to the maintainer that can
> > > take it?
> > i used scripts/get_maintainer.pl to get maintainers names and i am
> > adding all those people to the mail. kindly let me know the maintainer id
> > and the correct way to know the mainter of a file
>
> ./scripts/get_maintainer.pl ~/Downloads/PATCH-v3-staging-vt6655-Type-encoding-info-dropped-from-array-name-byVT3253B0_.txt
> Forest Bond <forest@alittletooquiet.net> (odd fixer:STAGING - VIA VT665X DRIVERS)
> Greg Kroah-Hartman <gregkh@linuxfoundation.org> (supporter:STAGING SUBSYSTEM,commit_signer:2/2=100%)
> Michael Straube <straube.linux@gmail.com> (commit_signer:2/2=100%,authored:2/2=100%,removed_lines:44/44=100%)
> linux-staging@lists.linux.dev (open list:STAGING SUBSYSTEM)
> linux-kernel@vger.kernel.org (open list)
>
> Greg shows up as one of the maintainers for me.
>
> Either a bug with get_maintainer.pl (unlikely), or you did something incorrectly.
>
> Best regards,
> Nam
yes. now it is showing Greg as maintainer for me too. i might have used
the script incorrectly earlier. added Greg to my mail while sending
next patch.
Thank you,
pavan
prev parent reply other threads:[~2023-09-11 12:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-07 13:10 [PATCH v3] staging: vt6655: Type encoding info dropped from array name "byVT3253B0_" Pavan Bobba
2023-09-07 14:43 ` Greg KH
2023-09-09 8:43 ` Pavan Bobba
2023-09-09 10:01 ` Nam Cao
2023-09-11 12:39 ` Pavan Bobba [this message]
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=ZP8Kakx1sUjnjWrQ@ubuntu.myguest.virtualbox.org \
--to=opensource206@gmail.com \
--cc=forest@alittletooquiet.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=namcaov@gmail.com \
--cc=straube.linux@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox