From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: Philipp Hortmann <philipp.g.hortmann@gmail.com>,
Pavan Bobba <opensource206@gmail.com>,
Forest Bond <forest@alittletooquiet.net>,
Michael Straube <straube.linux@gmail.com>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] staging: vt6655: Type encoding info dropped from array name "abyBBVGA"
Date: Thu, 5 Oct 2023 09:56:53 +0200 [thread overview]
Message-ID: <2023100513-handball-landed-d7ff@gregkh> (raw)
In-Reply-To: <76e75a6a-b3f5-4f96-a9c6-b01f8f491140@kadam.mountain>
On Fri, Sep 29, 2023 at 10:19:53AM +0300, Dan Carpenter wrote:
> On Thu, Sep 28, 2023 at 08:34:40PM +0200, Philipp Hortmann wrote:
> > On 9/28/23 17:06, Pavan Bobba wrote:
> > > array name "abyBBVGA" updated like below:
> > >
> > > a.type encoding info dropped from name
> > > b.camelcase name replaced by snakecase
> > >
> > > Issue found by checkpatch
> > >
> > > Signed-off-by: Pavan Bobba<opensource206@gmail.com>
> >
> >
> > A coverletter is missing.
> >
>
> The coverletter isn't required, but the more important issue is that the
> patchset wasn't sent as a thread but instead as separate emails.
I agree, our tools can not handl this.
Pavan, please resend these all as a patch series, properly threaded
together. Tools like 'git send-email' or 'b4' will do this for you
automatically.
thanks,
greg k-h
prev parent reply other threads:[~2023-10-05 7:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-28 15:06 [PATCH 1/3] staging: vt6655: Type encoding info dropped from array name "abyBBVGA" Pavan Bobba
2023-09-28 18:34 ` Philipp Hortmann
2023-09-29 7:19 ` Dan Carpenter
2023-10-05 7:56 ` Greg Kroah-Hartman [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=2023100513-handball-landed-d7ff@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=dan.carpenter@linaro.org \
--cc=forest@alittletooquiet.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=opensource206@gmail.com \
--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