From: Dave Penkler <dpenkler@gmail.com>
To: gregkh@linuxfoundation.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Cc: Dave Penkler <dpenkler@gmail.com>
Subject: [PATCH 0/4] staging: gpib: Clean up uapi include files
Date: Tue, 3 Jun 2025 20:43:16 +0200 [thread overview]
Message-ID: <20250603184320.30594-1-dpenkler@gmail.com> (raw)
This patch set addresses a number of issues identified in the
uapi include files.
Patch 1 - Remove enums and functions that are not needed to be
exported to user space.
Patch 2 - Add removed enums and functions dealing with GPIB
command bytes needed only by the kernel drivers in
a new local include file gpib_cmd.h
Patch 3 - Convert generic types to fixed size types in the
gpib_ioctl.h include file.
Patch 4 - Pad bit and byte holes in the ioctl structs.
Dave Penkler (4):
staging: gpib: Remove unneeded enums and functions
staging: gpib: Add local include file for commands
staging: gpib: Use standard size basic uapi types
staging: gpib: Add bit and byte padding to ioctl structs
drivers/staging/gpib/include/gpibP.h | 1 +
drivers/staging/gpib/include/gpib_cmd.h | 112 ++++++++++++++
drivers/staging/gpib/uapi/gpib.h | 198 ------------------------
drivers/staging/gpib/uapi/gpib_ioctl.h | 112 +++++++-------
4 files changed, 171 insertions(+), 252 deletions(-)
create mode 100644 drivers/staging/gpib/include/gpib_cmd.h
--
2.49.0
next reply other threads:[~2025-06-03 18:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-03 18:43 Dave Penkler [this message]
2025-06-03 18:43 ` [PATCH 1/4] staging: gpib: Remove unneeded enums and functions Dave Penkler
2025-06-03 18:43 ` [PATCH 2/4] staging: gpib: Add local include file for commands Dave Penkler
2025-06-03 18:43 ` [PATCH 3/4] staging: gpib: Use standard size basic uapi types Dave Penkler
2025-06-03 18:43 ` [PATCH 4/4] staging: gpib: Add bit and byte padding to ioctl structs Dave Penkler
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=20250603184320.30594-1-dpenkler@gmail.com \
--to=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