From: Michael Rubin <matchstick@neverthere.org>
To: gregkh@linuxfoundation.org, dpenkler@gmail.com
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
Michael Rubin <matchstick@neverthere.org>
Subject: [PATCH v2 00/14] staging: gpib: Adhering to Linux Code standards
Date: Wed, 16 Apr 2025 20:32:58 +0000 [thread overview]
Message-ID: <20250416203259.7862-1-matchstick@neverthere.org> (raw)
This is a remaining patch from a series of 14 to clean up the gpib driver to
adhere to Linux code style. The other 13 have been added to the tree but
this one requires a v2.
* Patch 1 - Fixing CamelCase for constants
Michael Rubin (1):
staging: gpib: uapi: Fix CamelCase and IBA Dup
drivers/staging/gpib/uapi/gpib_user.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
2.43.0
next reply other threads:[~2025-04-16 20:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-16 20:32 Michael Rubin [this message]
2025-04-16 20:32 ` [PATCH v2 10/14 1/1] staging: gpib: uapi: Fix CamelCase and IBA Dup Michael Rubin
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=20250416203259.7862-1-matchstick@neverthere.org \
--to=matchstick@neverthere.org \
--cc=dpenkler@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox