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: Create one base function for four macros
Date: Sat, 30 Jul 2022 21:20:10 +0200 [thread overview]
Message-ID: <cover.1659192760.git.philipp.g.hortmann@gmail.com> (raw)
Create one base function vt6655_mac_en_dis_bits_u32_reg with parameters for four multiline macros. Multiline macros are not liked by kernel community.
Tested with vt6655 on mini PCI Module
Transferred this patch over wlan connection of vt6655
Philipp Hortmann (6):
staging: vt6655: Convert macro MACvEnableProtectMD to function
staging: vt6655: Create one function for four macros
staging: vt6655: Rename function MACvEnableProtectMD
staging: vt6655: Convert macro MACvDisableProtectMD
staging: vt6655: Convert macro MACvEnableBarkerPreambleMd
staging: vt6655: Convert macro MACvDisableBarkerPreambleMd
drivers/staging/vt6655/device_main.c | 40 +++++++++++++++++++++++++---
drivers/staging/vt6655/mac.h | 37 +++----------------------
2 files changed, 40 insertions(+), 37 deletions(-)
--
2.37.1
next reply other threads:[~2022-07-30 19:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-30 19:20 Philipp Hortmann [this message]
2022-07-30 19:20 ` [PATCH 1/6] staging: vt6655: Convert macro MACvEnableProtectMD to function Philipp Hortmann
2022-07-30 19:20 ` [PATCH 2/6] staging: vt6655: Create one function for four macros Philipp Hortmann
2022-08-01 11:21 ` Dan Carpenter
2022-07-30 19:20 ` [PATCH 3/6] staging: vt6655: Rename function MACvEnableProtectMD Philipp Hortmann
2022-07-30 19:20 ` [PATCH 4/6] staging: vt6655: Convert macro MACvDisableProtectMD Philipp Hortmann
2022-07-30 19:20 ` [PATCH 5/6] staging: vt6655: Convert macro MACvEnableBarkerPreambleMd Philipp Hortmann
2022-07-30 19:21 ` [PATCH 6/6] staging: vt6655: Convert macro MACvDisableBarkerPreambleMd 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.1659192760.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.