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 09/18] staging: gpib: gpio: struct gpib_interface
Date: Wed, 16 Apr 2025 20:41:55 +0000 [thread overview]
Message-ID: <20250416204204.8009-10-matchstick@neverthere.org> (raw)
In-Reply-To: <20250416204204.8009-1-matchstick@neverthere.org>
Using Linux code style for struct gpib_interface.
Adhering 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.
Signed-off-by: Michael Rubin <matchstick@neverthere.org>
---
drivers/staging/gpib/gpio/gpib_bitbang.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/gpib/gpio/gpib_bitbang.c b/drivers/staging/gpib/gpio/gpib_bitbang.c
index 87622ee841c7..443d739c7edf 100644
--- a/drivers/staging/gpib/gpio/gpib_bitbang.c
+++ b/drivers/staging/gpib/gpio/gpib_bitbang.c
@@ -1308,7 +1308,7 @@ static int bb_attach(struct gpib_board *board, const struct gpib_board_config *c
return retval;
}
-static gpib_interface_t bb_interface = {
+static struct gpib_interface bb_interface = {
.name = NAME,
.attach = bb_attach,
.detach = bb_detach,
--
2.43.0
next prev parent reply other threads:[~2025-04-16 20:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-16 20:41 [PATCH v2 00/18] staging: gpib: Removing typedef of gpib_interface_t Michael Rubin
2025-04-16 20:41 ` [PATCH v2 01/18] staging: gpib: struct typing for gpib_interface Michael Rubin
2025-04-16 20:41 ` [PATCH v2 02/18] staging: gpib: agilent_82350b: gpib_interface Michael Rubin
2025-04-16 20:41 ` [PATCH v2 03/18] staging: gpib: agilent_82357a: gpib_interface Michael Rubin
2025-04-16 20:41 ` [PATCH v2 04/18] staging: gpib: cb7210: struct gpib_interface Michael Rubin
2025-04-16 20:41 ` [PATCH v2 05/18] staging: gpib: cec: " Michael Rubin
2025-04-16 20:41 ` [PATCH v2 06/18] staging: gpib: common: " Michael Rubin
2025-04-16 20:41 ` [PATCH v2 07/18] staging: gpib: fluke: " Michael Rubin
2025-04-16 20:41 ` [PATCH v2 08/18] staging: gpib: fmh: " Michael Rubin
2025-04-16 20:41 ` Michael Rubin [this message]
2025-04-16 20:41 ` [PATCH v2 10/18] staging: gpib: hp_82335: " Michael Rubin
2025-04-16 20:41 ` [PATCH v2 11/18] staging: gpib: hp2341: " Michael Rubin
2025-04-16 20:41 ` [PATCH v2 12/18] staging: gpib: gpibP: " Michael Rubin
2025-04-16 20:41 ` [PATCH v2 13/18] staging: gpib: ines: " Michael Rubin
2025-04-16 20:42 ` [PATCH v2 14/18] staging: gpib: lpvo_usb: " Michael Rubin
2025-04-16 20:42 ` [PATCH v2 15/18] staging: gpib: ni_usb: " Michael Rubin
2025-04-16 20:42 ` [PATCH v2 16/18] staging: gpib: pc2: " Michael Rubin
2025-04-16 20:42 ` [PATCH v2 17/18] staging: gpib: tnt4882: " Michael Rubin
2025-04-16 20:42 ` [PATCH v2 18/18] staging: gpib: Removing typedef gpib_interface_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=20250416204204.8009-10-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