From: Pavel Skripkin <paskripkin@gmail.com>
To: Philipp Hortmann <philipp.g.hortmann@gmail.com>,
Forest Bond <forest@alittletooquiet.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/7] staging: vt6655: Remove unused macros with CamelCase in mac.h
Date: Sun, 3 Apr 2022 14:40:34 +0300 [thread overview]
Message-ID: <0107f709-49ad-a0c3-916d-0f7b32991a0d@gmail.com> (raw)
In-Reply-To: <646acd285c1239f301692456bd9f46eda449d02b.1648882847.git.philipp.g.hortmann@gmail.com>
Hi Philipp,
On 4/2/22 10:29, Philipp Hortmann wrote:
> Remove unused macros with CamelCase variables in mac.h as
> they are not accepted by checkpatch.pl
>
> Signed-off-by: Philipp Hortmann <philipp.g.hortmann@gmail.com>
> ---
You can merge 1/7 and 2/7, since you are just removing unused macros in
same file.
With regards,
Pavel Skripkin
next prev parent reply other threads:[~2022-04-03 11:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-02 7:29 [PATCH 0/7] staging: vt6655: Fix CamelCase in upc.h and started " Philipp Hortmann
2022-04-02 7:29 ` [PATCH 1/7] staging: vt6655: Remove unused macros with do while(0) Philipp Hortmann
2022-04-02 7:29 ` [PATCH 2/7] staging: vt6655: Remove unused macros with CamelCase in mac.h Philipp Hortmann
2022-04-03 11:40 ` Pavel Skripkin [this message]
2022-04-02 7:29 ` [PATCH 3/7] staging: vt6655: Rename constant definitions with CamelCase Philipp Hortmann
2022-04-02 7:29 ` [PATCH 4/7] staging: vt6655: Rename macro arguments " Philipp Hortmann
2022-04-02 7:29 ` [PATCH 5/7] staging: vt6655: Rename macros VNSvInPortB,W,D Philipp Hortmann
2022-04-02 7:29 ` [PATCH 6/7] staging: vt6655: Rename macros VNSvOutPortB,W,D Philipp Hortmann
2022-04-02 7:29 ` [PATCH 7/7] staging: vt6655: Convert macro PCAvDelayByIO to function Philipp Hortmann
2022-04-02 11:05 ` kernel test robot
2022-04-03 11:16 ` Greg Kroah-Hartman
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=0107f709-49ad-a0c3-916d-0f7b32991a0d@gmail.com \
--to=paskripkin@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 \
/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
all inboxes | Powered by JetHome®