From: Dave Penkler <dpenkler@gmail.com>
To: gregkh@linuxfoundation.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Cc: dan.carpenter@linaro.org, Dave Penkler <dpenkler@gmail.com>
Subject: [PATCH 0/2] Driver entry point clean-up
Date: Wed, 22 Jan 2025 11:38:57 +0100 [thread overview]
Message-ID: <20250122103859.25499-1-dpenkler@gmail.com> (raw)
These patches make the driver entry points static and tries
to minimize the number of forward declarations.
In the course of the cleanup a missing entry point in the
interface structures of the agilent_82350b driver was
discovered.
Patch 1 fixes the missing entry point.
Patch 2 makes the driver entry points static and moves
the interface structures to the end of the drivers
where needed.
Dave Penkler (2):
staging: gpib: Add missing interface entry point
staging: gpib: Make static and reduce forward declarations
.../gpib/agilent_82350b/agilent_82350b.c | 110 ++-
.../gpib/agilent_82350b/agilent_82350b.h | 47 --
drivers/staging/gpib/cb7210/cb7210.c | 89 ++-
drivers/staging/gpib/cb7210/cb7210.h | 45 --
drivers/staging/gpib/cec/cec.h | 29 -
drivers/staging/gpib/cec/cec_gpib.c | 51 +-
drivers/staging/gpib/hp_82335/hp82335.c | 52 +-
drivers/staging/gpib/hp_82335/hp82335.h | 30 -
drivers/staging/gpib/hp_82341/hp_82341.c | 71 +-
drivers/staging/gpib/hp_82341/hp_82341.h | 40 -
drivers/staging/gpib/pc2/pc2_gpib.c | 247 +++---
drivers/staging/gpib/tnt4882/tnt4882_gpib.c | 718 ++++++++----------
12 files changed, 638 insertions(+), 891 deletions(-)
--
2.47.1
next reply other threads:[~2025-01-22 10:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-22 10:38 Dave Penkler [this message]
2025-01-22 10:38 ` [PATCH 1/2] staging: gpib: Add missing interface entry point Dave Penkler
2025-01-22 10:38 ` [PATCH 2/2] staging: gpib: Make static, reduce fwd declarations Dave Penkler
2025-01-22 11:34 ` [PATCH 0/2] Driver entry point clean-up Dan Carpenter
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=20250122103859.25499-1-dpenkler@gmail.com \
--to=dpenkler@gmail.com \
--cc=dan.carpenter@linaro.org \
--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