From: Dave Penkler <dpenkler@gmail.com>
To: Michael Rubin <matchstick@neverthere.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 0/2] Correct CamelCase drivers/staging/gpib
Date: Thu, 20 Mar 2025 09:16:40 +0100 [thread overview]
Message-ID: <Z9vO6CyFBNzTpvjO@egonzo> (raw)
In-Reply-To: <20250319211827.9854-1-matchstick@neverthere.org>
On Wed, Mar 19, 2025 at 09:18:25PM +0000, Michael Rubin wrote:
> staging: gpib: Correct CamelCase and remove duplicate entries for bus control
> lines.
>
> Adhere to Linux kernel coding style.
>
> Reported by checkpatch
>
> CHECK: Avoid CamelCase
>
> * Patch 1: "staging: gpib: Correct CamelCase for BUS constants"
> * Removes duplicate entries and corrcts Bus with BUS
>
> * Patch 2: "staging: gpib: Correct CamelCase for VALID enums"
> * Replaces Valid with VALID
>
> [PATCH v1 01/02] staging: gpib: Correct CamelCase for BUS constants
> [PATCH v1 02/02] staging: gpib: Correct CamelCase for VALID enums
>
> Michael Rubin (2):
> .../gpib/agilent_82357a/agilent_82357a.c | 18 ++++++------
> drivers/staging/gpib/cb7210/cb7210.c | 18 ++++++------
> drivers/staging/gpib/common/iblib.c | 8 ++---
> drivers/staging/gpib/eastwood/fluke_gpib.c | 18 ++++++------
> drivers/staging/gpib/fmh_gpib/fmh_gpib.c | 18 ++++++------
> drivers/staging/gpib/gpio/gpib_bitbang.c | 18 ++++++------
> drivers/staging/gpib/hp_82341/hp_82341.c | 2 +-
> drivers/staging/gpib/ines/ines_gpib.c | 18 ++++++------
> .../gpib/lpvo_usb_gpib/lpvo_usb_gpib.c | 18 ++++++------
> drivers/staging/gpib/ni_usb/ni_usb_gpib.c | 18 ++++++------
> drivers/staging/gpib/tms9914/tms9914.c | 18 ++++++------
> drivers/staging/gpib/tnt4882/tnt4882_gpib.c | 18 ++++++------
> drivers/staging/gpib/uapi/gpib_user.h | 29 ++++++-------------
> 13 files changed, 104 insertions(+), 115 deletions(-)
>
> --
> 2.43.0
>
I will be releasing a new user part and will make a compat include there.
Acked-By: Dave Penkler <dpenkler@gmail.com>
prev parent reply other threads:[~2025-03-20 8:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-19 21:18 [PATCH v1 0/2] Correct CamelCase drivers/staging/gpib Michael Rubin
2025-03-19 21:18 ` [PATCH v1 1/2] staging: gpib: Correct CamelCase for BUS constants Michael Rubin
2025-03-19 21:18 ` [PATCH v1 2/2] staging: gpib: Correct CamelCase for VALID enums Michael Rubin
2025-03-20 8:16 ` Dave Penkler [this message]
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=Z9vO6CyFBNzTpvjO@egonzo \
--to=dpenkler@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=matchstick@neverthere.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