From: Philipp Hortmann <philipp.g.hortmann@gmail.com>
To: Forest Bond <forest@alittletooquiet.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: [PATCH 0/6] staging: vt6655: Convert two macros to static functions
Date: Mon, 4 Jul 2022 20:20:19 +0200 [thread overview]
Message-ID: <cover.1656835310.git.philipp.g.hortmann@gmail.com> (raw)
Convert two multiline macros used only once to static functions.
checkpatch.pl does not accept multiline macros.
Tested with vt6655 on mini PCI Module
Transferred this patch over wlan connection of vt6655
Philipp Hortmann (6):
staging: vt6655: Rename pbyEtherAddr to mac_addr
staging: vt6655: Rename MACvWriteBSSIDAddress
staging: vt6655: Rename MACvReadEtherAddress
staging: vt6655: Move two macros to file where those are used
staging: vt6655: Convert macro vt6655_mac_write_bssid_addr to function
staging: vt6655: Convert macro vt6655_mac_read_ether_addr to function
drivers/staging/vt6655/device_main.c | 31 ++++++++++++++++++++++++++--
drivers/staging/vt6655/mac.h | 24 ---------------------
2 files changed, 29 insertions(+), 26 deletions(-)
--
2.36.1
next reply other threads:[~2022-07-04 18:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-04 18:20 Philipp Hortmann [this message]
2022-07-04 18:20 ` [PATCH 1/6] staging: vt6655: Rename pbyEtherAddr to mac_addr Philipp Hortmann
2022-07-04 19:05 ` Joe Perches
2022-07-04 18:20 ` [PATCH 2/6] staging: vt6655: Rename MACvWriteBSSIDAddress Philipp Hortmann
2022-07-04 18:20 ` [PATCH 3/6] staging: vt6655: Rename MACvReadEtherAddress Philipp Hortmann
2022-07-04 18:20 ` [PATCH 4/6] staging: vt6655: Move two macros to file where those are used Philipp Hortmann
2022-07-04 18:20 ` [PATCH 5/6] staging: vt6655: Convert macro vt6655_mac_write_bssid_addr to function Philipp Hortmann
2022-07-04 18:21 ` [PATCH 6/6] staging: vt6655: Convert macro vt6655_mac_read_ether_addr " Philipp Hortmann
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=cover.1656835310.git.philipp.g.hortmann@gmail.com \
--to=philipp.g.hortmann@gmail.com \
--cc=forest@alittletooquiet.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).