From: Pavan Bobba <opensource206@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Forest Bond <forest@alittletooquiet.net>,
Michael Straube <straube.linux@gmail.com>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] staging: vt6655: Type encoding info dropped from array name "byVT3253B0_"
Date: Wed, 13 Sep 2023 17:16:38 +0530 [thread overview]
Message-ID: <ZQGhHj0q5ISLkfzN@ubuntu.myguest.virtualbox.org> (raw)
In-Reply-To: <2023091210-wok-laziness-b64e@gregkh>
On Tue, Sep 12, 2023 at 03:58:32PM +0200, Greg Kroah-Hartman wrote:
> On Mon, Sep 11, 2023 at 06:01:55PM +0530, Pavan Bobba wrote:
> > Array names starting with "byVT3253B0_" updated like below:
> >
> > a.type encoding info dropped from names
> > b.camelcase 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
> >
> > v3 -> v4: changelog modified as per patch submission guidelines
> >
>
> I see 2 v4 patches on the mailing list, sent on different days. Which
> one is correct?
>
> I'll drop both and wait for a v5.
>
> thanks,
>
> greg k-h
apologies for the confusion greg. second v4 patch i sent since
in first v4 patch mail , you are not there in mail receipents.
anyway, i will send v5 to avoid confusion
thanks,
pavan
next prev parent reply other threads:[~2023-09-13 11:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 12:31 [PATCH v4] staging: vt6655: Type encoding info dropped from array name "byVT3253B0_" Pavan Bobba
2023-09-12 13:58 ` Greg Kroah-Hartman
2023-09-13 11:46 ` Pavan Bobba [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-09 9:57 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=ZQGhHj0q5ISLkfzN@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=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