From: Soumya Negi <soumya.negi97@gmail.com>
To: Martyn Welch <martyn@welchs.me.uk>,
Manohar Vanga <manohar.vanga@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: outreachy@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-staging@lists.linux.dev,
Soumya Negi <soumya.negi97@gmail.com>
Subject: [PATCH 0/4] staging: vme_user: Coding style cleanup patches
Date: Fri, 13 Oct 2023 16:47:12 -0700 [thread overview]
Message-ID: <cover.1697240381.git.soumya.negi97@gmail.com> (raw)
This patchset performs trivial code cleanups on the driver
staging/vme_user to improve code readability. All patches address
issues reported by checkpatch.pl, and may be applied in any sequence.
Soumya Negi (4):
staging: vme_user: Correct spelling mistakes in comments
staging: vme_user: Fix unbalanced {} in if-else blocks
staging: vme_user: Add spaces around '*'
staging: vme_user: Add spaces around '<<' operator
drivers/staging/vme_user/vme.c | 7 +-
drivers/staging/vme_user/vme.h | 2 +-
drivers/staging/vme_user/vme_tsi148.c | 7 +-
drivers/staging/vme_user/vme_tsi148.h | 548 +++++++++++++-------------
4 files changed, 283 insertions(+), 281 deletions(-)
--
2.42.0
next reply other threads:[~2023-10-13 23:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-13 23:47 Soumya Negi [this message]
2023-10-13 23:47 ` [PATCH 1/4] staging: vme_user: Correct spelling mistakes in comments Soumya Negi
2023-10-13 23:47 ` [PATCH 2/4] staging: vme_user: Fix unbalanced {} in if-else blocks Soumya Negi
2023-10-13 23:47 ` [PATCH 3/4] staging: vme_user: Add spaces around '*' Soumya Negi
2023-10-13 23:47 ` [PATCH 4/4] staging: vme_user: Add spaces around '<<' operator Soumya Negi
2023-10-14 20:02 ` [PATCH 0/4] staging: vme_user: Coding style cleanup patches Soumya Negi
2023-10-15 5:29 ` Andi Shyti
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.1697240381.git.soumya.negi97@gmail.com \
--to=soumya.negi97@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=manohar.vanga@gmail.com \
--cc=martyn@welchs.me.uk \
--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 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 read-only IMAP folder(s) and NNTP newsgroup(s).