mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michael Rubin <matchstick@neverthere.org>
To: gregkh@linuxfoundation.org, dpenkler@gmail.com,
	linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Cc: Michael Rubin <matchstick@neverthere.org>
Subject: [PATCH v1 18/18] staging: gpib: Removing typedef gpib_board_config
Date: Tue,  8 Apr 2025 22:36:58 +0000	[thread overview]
Message-ID: <20250408223659.187109-19-matchstick@neverthere.org> (raw)
In-Reply-To: <20250408223659.187109-1-matchstick@neverthere.org>

Removing gpib_interface_t 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.

Signed-off-by: Michael Rubin <matchstick@neverthere.org>
---
 drivers/staging/gpib/include/gpib_types.h | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/drivers/staging/gpib/include/gpib_types.h b/drivers/staging/gpib/include/gpib_types.h
index 1c641f17bdeb..0253ef2c94a3 100644
--- a/drivers/staging/gpib/include/gpib_types.h
+++ b/drivers/staging/gpib/include/gpib_types.h
@@ -23,7 +23,6 @@
 #include <linux/interrupt.h>
 
 struct gpib_board;
-typedef struct gpib_board_config gpib_board_config_t;
 
 /* config parameters that are only used by driver attach functions */
 struct gpib_board_config {
@@ -55,7 +54,7 @@ struct gpib_interface {
 	/* name of board */
 	char *name;
 	/* attach() initializes board and allocates resources */
-	int (*attach)(struct gpib_board *board, const gpib_board_config_t *config);
+	int (*attach)(struct gpib_board *board, const struct gpib_board_config *config);
 	/* detach() shuts down board and frees resources */
 	void (*detach)(struct gpib_board *board);
 	/* read() should read at most 'length' bytes from the bus into
@@ -291,7 +290,7 @@ struct gpib_board {
 	struct gpib_pseudo_irq pseudo_irq;
 	/* error dong autopoll */
 	atomic_t stuck_srq;
-	gpib_board_config_t config;
+	struct gpib_board_config config;
 	/* Flag that indicates whether board is system controller of the bus */
 	unsigned master : 1;
 	/* individual status bit */
-- 
2.43.0


      parent reply	other threads:[~2025-04-08 22:37 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-08 22:36 [PATCH v1 00/18] staging: gpib: Removing typedef gpib_board_config_t Michael Rubin
2025-04-08 22:36 ` [PATCH v1 01/18] staing: gpib: struct typing for gpib_board_config Michael Rubin
2025-04-08 22:36 ` [PATCH v1 02/18] staging: gpib: agilent_82350b: gpib_board_config Michael Rubin
2025-04-08 22:36 ` [PATCH v1 03/18] staging: gpib: agilent_82357a: gpib_board_config Michael Rubin
2025-04-08 22:36 ` [PATCH v1 04/18] staging: gpib: cb7210: struct gpib_board_config Michael Rubin
2025-04-08 22:36 ` [PATCH v1 05/18] staging: gpib: cec: " Michael Rubin
2025-04-08 22:36 ` [PATCH v1 06/18] staging: gpib: common: " Michael Rubin
2025-04-08 22:36 ` [PATCH v1 07/18] staging: gpib: eastwood: " Michael Rubin
2025-04-08 22:36 ` [PATCH v1 08/18] staging: gpib: fmh: " Michael Rubin
2025-04-08 22:36 ` [PATCH v1 09/18] staging: gpib: gpio: " Michael Rubin
2025-04-08 22:36 ` [PATCH v1 10/18] staging: gpib: hp_82335: " Michael Rubin
2025-04-08 22:36 ` [PATCH v1 11/18] staging: gpib: hp_82341: " Michael Rubin
2025-04-08 22:36 ` [PATCH v1 12/18] staging: gpib: gpibP: " Michael Rubin
2025-04-08 22:36 ` [PATCH v1 13/18] staging: gpib: ines: " Michael Rubin
2025-04-08 22:36 ` [PATCH v1 14/18] staging: gpib: lpvo_usb: " Michael Rubin
2025-04-08 22:36 ` [PATCH v1 15/18] staging: gpib: ni_usb: " Michael Rubin
2025-04-08 22:36 ` [PATCH v1 16/18] staging: gpib: pc2: " Michael Rubin
2025-04-08 22:36 ` [PATCH v1 17/18] staging: gpib: tnt4882: " Michael Rubin
2025-04-08 22:36 ` Michael Rubin [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=20250408223659.187109-19-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®