From: Pavan Bobba <opensource206@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Forest Bond <forest@alittletooquiet.net>,
Michael Straube <straube.linux@gmail.com>,
Philipp Hortmann <philipp.g.hortmann@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: Sat, 9 Sep 2023 14:13:09 +0530 [thread overview]
Message-ID: <ZPwwHY1TDOBEljxr@ubuntu.myguest.virtualbox.org> (raw)
In-Reply-To: <2023090724-trial-ipod-93d2@gregkh>
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
>
> Also, your changelog needs work, please read the link the bot referred
> you to.
>
> thanks,
>
> greg k-h
sure. i will cross check once. Thank you
next prev parent reply other threads:[~2023-09-09 8:43 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 [this message]
2023-09-09 10:01 ` Nam Cao
2023-09-11 12:39 ` Pavan Bobba
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=ZPwwHY1TDOBEljxr@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=philipp.g.hortmann@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