From: Nam Cao <namcaov@gmail.com>
To: gregkh@linuxfoundation.org
Cc: dan.carpenter@oracle.com, linux-kernel@vger.kernel.org,
linux-staging@lists.linux.dev, namcaov@gmail.com,
phil@philpotter.co.uk, Larry.Finger@lwfinger.net,
paskripkin@gmail.com
Subject: [PATCH v3 0/2] get rid of confusing macros
Date: Tue, 14 Jun 2022 17:58:43 +0200 [thread overview]
Message-ID: <cover.1655220367.git.namcaov@gmail.com> (raw)
In-Reply-To: <YqhWIiXadDC3hzel@kroah.com>
Replace some confusing macros with more explicit codes.
V3:
- Get rid of GET_TX_REPORT_TYPE1_RERTY_0 and similar
V2:
- Split into smaller commits so that it's easier to review
Nam Cao (2):
staging: r8188eu: replace confusing macros
staging: r8188eu: remove unused macros
.../r8188eu/hal/Hal8188ERateAdaptive.c | 12 +++----
.../r8188eu/include/Hal8188ERateAdaptive.h | 13 --------
drivers/staging/r8188eu/include/basic_types.h | 31 -------------------
3 files changed, 6 insertions(+), 50 deletions(-)
--
2.25.1
next prev parent reply other threads:[~2022-06-14 15:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-12 1:05 [PATCH 0/2] Clean up some macros Nam Cao
2022-06-12 1:05 ` [PATCH 1/2] staging: r8188eu: simplify " Nam Cao
2022-06-12 4:56 ` Greg KH
2022-06-12 8:11 ` [PATCH v2 0/2] " Nam Cao
2022-06-12 8:11 ` [PATCH v2 1/2] staging: r8188eu: replace LE_BITS_TO_1BYTE with clearer codes Nam Cao
2022-06-13 14:30 ` Dan Carpenter
2022-06-14 9:34 ` Greg KH
2022-06-14 15:58 ` Nam Cao [this message]
2022-06-14 15:58 ` [PATCH v3 1/2] staging: r8188eu: replace confusing macros Nam Cao
2022-06-14 15:58 ` [PATCH v3 2/2] staging: r8188eu: remove unused macros Nam Cao
2022-06-15 8:29 ` [PATCH v3 0/2] get rid of confusing macros Dan Carpenter
2022-06-12 8:11 ` [PATCH v2 2/2] staging: r8188eu: remove unused macros Nam Cao
2022-06-12 1:05 ` [PATCH 2/2] staging: r8188eu: replace FIELD_OFFSET with offsetof Nam Cao
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.1655220367.git.namcaov@gmail.com \
--to=namcaov@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=dan.carpenter@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=paskripkin@gmail.com \
--cc=phil@philpotter.co.uk \
/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.