From: Rachit Dhar <rchtdhr@gmail.com>
Cc: Rachit Dhar <rchtdhr@gmail.com>,
Viresh Kumar <vireshk@kernel.org>,
Johan Hovold <johan@kernel.org>, Alex Elder <elder@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rui Miguel Silva <rmfrfs@gmail.com>,
greybus-dev@lists.linaro.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: [PATCH v4 0/2] staging: greybus: fixing checkpatch issues
Date: Sat, 7 Mar 2026 14:09:23 +0000 [thread overview]
Message-ID: <20260307140930.1732-1-rchtdhr@gmail.com> (raw)
This series fixes some of the checkpatch.pl checks
highlighted in greybus.
Changes in v4:
- As per the suggestions of Greg K.H., I am removing two patches
that added comments to mutex declarations, since it is hard to
verify them, without extensive analysis and documentation.
- The patches were sent out-of-order previously, so will
try sending them all together this time.
Changes in v3:
- Added cover letter detailing changes made in subsequent versions of
patch-sets.
- v2 patch-set was only emailed to maintainers. The email was forwarded
to the lists, but this rendered the patch-set corrupted. v3 hopes to
correct this.
Changes in v2:
- Split patch 1 into two individual patches 1/4 and 2/4 to keep logical
changes separate.
Rachit Dhar (2):
staging: greybus: fixed styling issue in fw-management.c
staging: greybus: resolved checkpatch checks for light.c
drivers/staging/greybus/fw-management.c | 3 ++-
drivers/staging/greybus/light.c | 4 ++--
2 files changed, 4 insertions(+), 3 deletions(-)
--
2.43.0
next reply other threads:[~2026-03-07 14:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-07 14:09 Rachit Dhar [this message]
2026-03-07 14:09 ` [PATCH v4 1/2] staging: greybus: fixed styling issue in fw-management.c Rachit Dhar
2026-03-07 14:09 ` [PATCH v4 2/2] staging: greybus: resolved checkpatch checks for light.c Rachit Dhar
2026-03-07 14:39 ` Dan Carpenter
2026-03-07 14:44 ` Dan Carpenter
2026-03-08 18:48 ` [PATCH v4 0/2] staging: greybus: fixing checkpatch issues 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=20260307140930.1732-1-rchtdhr@gmail.com \
--to=rchtdhr@gmail.com \
--cc=elder@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=greybus-dev@lists.linaro.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=rmfrfs@gmail.com \
--cc=vireshk@kernel.org \
/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