From: Philipp Hortmann <philipp.g.hortmann@gmail.com>
To: Pavan Bobba <opensource206@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 0/3] Type encoding info dropped from arrary name "abyBBVGA" and variable names "byBBVGACurrent", "byBBVGANew"
Date: Sat, 14 Oct 2023 08:11:57 +0200 [thread overview]
Message-ID: <bac0d5b5-9c6e-4892-b328-bc998add7f64@gmail.com> (raw)
In-Reply-To: <cover.1696791459.git.opensource206@gmail.com>
On 10/8/23 21:01, Pavan Bobba wrote:
> This patchset series consist of fixes to issues found by checkpatch
>
> Pavan Bobba (3):
> staging: vt6655: Type encoding info dropped from array name "abyBBVGA"
> staging: vt6655: Type encoding info dropped from variable name
> "byBBVGACurrent"
> staging: vt6655: Type encoding info dropped from variable name
> "byBBVGANew"
>
> drivers/staging/vt6655/baseband.c | 40 ++++++++++++++--------------
> drivers/staging/vt6655/channel.c | 6 ++---
> drivers/staging/vt6655/device.h | 6 ++---
> drivers/staging/vt6655/device_main.c | 24 ++++++++---------
> 4 files changed, 38 insertions(+), 38 deletions(-)
>
Tested-by: Philipp Hortmann <philipp.g.hortmann@gmail.com>
prev parent reply other threads:[~2023-10-14 6:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-08 19:01 [PATCH v5 0/3] Type encoding info dropped from arrary name "abyBBVGA" and variable names "byBBVGACurrent", "byBBVGANew" Pavan Bobba
2023-10-08 19:01 ` [PATCH v5 1/3] staging: vt6655: Type encoding info dropped from array name "abyBBVGA" Pavan Bobba
2023-10-08 19:01 ` [PATCH v5 2/3] staging: vt6655: Type encoding info dropped from variable name "byBBVGACurrent" Pavan Bobba
2023-10-08 19:01 ` [PATCH v5 3/3] staging: vt6655: Type encoding info dropped from variable name "byBBVGANew" Pavan Bobba
2023-10-14 6:11 ` Philipp Hortmann [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=bac0d5b5-9c6e-4892-b328-bc998add7f64@gmail.com \
--to=philipp.g.hortmann@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=opensource206@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