From: Emily Peri <eperi1024@gmail.com>
To: gregkh@linuxfoundation.org, outreachy@lists.linux.dev,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Cc: Emily Peri <eperi1024@gmail.com>
Subject: [PATCH v2 0/3] clean up driver code in rtw_ioctl_set
Date: Fri, 21 Oct 2022 12:54:54 -0700 [thread overview]
Message-ID: <cover.1666380274.git.eperi1024@gmail.com> (raw)
Created patchset to fix all checkpatch warnings in rtw_ioctl_set
Changes since v1:
* Patch 1: "staging: rtl8723bs: remove tab in variable definition"
* Split previous white space patch into three separate patches
(feedback from Gregh). Remove tab instead of space (feedback from
Michael S and Praveen K)
* Patch 2: "staging: rtl8723bs: add newline after variable declaration"
* Split previous white space patch into three separate patches
(feedback from Gregh).
* Patch 3: "staging: rtl8723bs: use tab instead of spaces for indent"
* Split previous white space patch into three separate patches
(feedback from Gregh).
* Merged into Greg's tree "rtl8723bs: align block comment stars"
* Merged into Greg's tree "staging: rtl8723bs: remove unnecessary parenthesis"
Emily Peri (3):
staging: rtl8723bs: remove tab in variable definition
staging: rtl8723bs: add newline after variable declaration
staging: rtl8723bs: use tab instead of spaces for indent
drivers/staging/rtl8723bs/core/rtw_ioctl_set.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
--
2.34.1
next reply other threads:[~2022-10-21 19:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-21 19:54 Emily Peri [this message]
2022-10-21 19:54 ` [PATCH v2 1/3] staging: rtl8723bs: remove tab in variable definition Emily Peri
2022-10-21 19:54 ` [PATCH v2 2/3] staging: rtl8723bs: add newline after variable declaration Emily Peri
2022-10-21 19:54 ` [PATCH v2 3/3] staging: rtl8723bs: use tab instead of spaces for indent Emily Peri
2022-10-22 8:07 ` [PATCH v2 0/3] clean up driver code in rtw_ioctl_set Greg KH
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.1666380274.git.eperi1024@gmail.com \
--to=eperi1024@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=outreachy@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.