From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Pavan Bobba <opensource206@gmail.com>
Cc: Forest Bond <forest@alittletooquiet.net>,
Michael Straube <straube.linux@gmail.com>,
Philipp Hortmann <philipp.g.hortmann@gmail.com>,
outreachy@lists.linux.dev, linux-staging@lists.linux.dev,
linuxkernel@vger.kernel.org
Subject: Re: [PATCH v2] staging: vt6655: replace camel case by snake case
Date: Fri, 4 Aug 2023 15:22:05 +0200 [thread overview]
Message-ID: <2023080451-sauciness-observer-fdf7@gregkh> (raw)
In-Reply-To: <ZMzmrADhbNCZFm5f@ubuntu.myguest.virtualbox.org>
On Fri, Aug 04, 2023 at 05:23:16PM +0530, Pavan Bobba wrote:
> >From 15487baaf86627009a06ab5217428d3b29028c32 Mon Sep 17 00:00:00 2001
> From: Pavan Bobba <opensource206@gmail.com>
> Date: Wed, 2 Aug 2023 18:12:56 +0530
> Subject: [PATCH v2] staging: vt6655: replace camel case by snake case
This shouldn't be in the email body :(
thanks,
greg k-h
next prev parent reply other threads:[~2023-08-04 13:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-02 13:26 [PATCH] staging: vt6655: replace camel case by small case Pavan Bobba
2023-08-02 13:33 ` Dan Carpenter
2023-08-04 11:53 ` [PATCH v2] staging: vt6655: replace camel case by snake case Pavan Bobba
2023-08-04 12:01 ` Dan Carpenter
2023-08-04 13:22 ` Greg Kroah-Hartman [this message]
2023-08-02 16:33 ` [PATCH] staging: vt6655: replace camel case by small case Nam Cao
-- strict thread matches above, loose matches on Subject: below --
2023-08-05 8:59 [PATCH v2] staging: vt6655: replace camel case by snake case Pavan Bobba
2023-08-05 16:30 ` Dan Carpenter
2023-08-09 12:20 ` Greg KH
2023-08-09 12:47 Pavan Bobba
2023-08-11 21:27 ` Greg KH
2023-08-12 18:29 ` Pavan Bobba
2023-08-12 18:41 ` Julia Lawall
2023-08-14 13:02 ` Pavan Bobba
2023-08-14 15:20 ` Greg KH
2023-08-17 12:08 ` Pavan Bobba
2023-08-23 12:53 Pavan Bobba
2023-08-23 12:58 ` Julia Lawall
2023-08-23 13:32 ` Pavan Bobba
2023-08-23 13:58 ` Greg KH
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=2023080451-sauciness-observer-fdf7@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=forest@alittletooquiet.net \
--cc=linux-staging@lists.linux.dev \
--cc=linuxkernel@vger.kernel.org \
--cc=opensource206@gmail.com \
--cc=outreachy@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