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 v1 0/7] staging: gpib: Removing typedefs
Date: Tue, 8 Apr 2025 23:25:28 +0000 [thread overview]
Message-ID: <20250408232535.187528-1-matchstick@neverthere.org> (raw)
Removing various typedefs to adhere to Linux code style.
Reported by checkpatch.pl
In general, a pointer, or a struct that has elements that can reasonably be
directly accessed should never be a typedef.
* Patch 1: Removing gpib_event_queue_t for struct gpib_event_queue
* Patch 2: Removing gpib_interface_list_t for struct gpib_interface_list
* Patch 3: Removing gpib_event_t for struct gpib_event
* Patch 4: Removing gpib_status_queue_t for struct gpib_status_queue
* Patch 5: Removing status_byte_t for struct gpib_status_bye
* Patch 6: Removing gpib_descriptor_t for struct gpib_descriptor
* Patch 7: Removing gpib_file_private_t for struct gpib_file_private
Michael Rubin (7):
staging: gpib: Removing typedef gpib_event_queue
staging: gpib: Removing gpib_interface_list_t
staging: gpib: Removing gpib_event_t typedef
staging: gpib: Removing typedef gpib_status_queue
staging: gpib: Removing typedef of status_byte
staging: gpib: Removing typedef gpib_descriptor_t
staging: gpib: Remove typedef gpib_file_private_t
drivers/staging/gpib/common/gpib_os.c | 155 +++++++++++-----------
drivers/staging/gpib/common/iblib.c | 12 +-
drivers/staging/gpib/common/ibsys.h | 11 +-
drivers/staging/gpib/include/gpibP.h | 4 +-
drivers/staging/gpib/include/gpib_proto.h | 8 +-
drivers/staging/gpib/include/gpib_types.h | 38 +++---
6 files changed, 116 insertions(+), 112 deletions(-)
--
2.43.0
next reply other threads:[~2025-04-08 23:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-08 23:25 Michael Rubin [this message]
2025-04-08 23:25 ` [PATCH v1 1/7] staging: gpib: Removing typedef gpib_event_queue Michael Rubin
2025-04-08 23:25 ` [PATCH v1 2/7] staging: gpib: Removing gpib_interface_list_t Michael Rubin
2025-04-08 23:25 ` [PATCH v1 3/7] staging: gpib: Removing gpib_event_t typedef Michael Rubin
2025-04-08 23:25 ` [PATCH v1 4/7] staging: gpib: Removing typedef gpib_status_queue Michael Rubin
2025-04-08 23:25 ` [PATCH v1 5/7] staging: gpib: Removing typedef of status_byte Michael Rubin
2025-04-08 23:25 ` [PATCH v1 6/7] staging: gpib: Removing typedef gpib_descriptor_t Michael Rubin
2025-04-08 23:25 ` [PATCH v1 7/7] staging: gpib: Remove typedef gpib_file_private_t 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=20250408232535.187528-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
all inboxes | Powered by JetHome®