From: Dave Penkler <dpenkler@gmail.com>
To: Arnd Bergmann <arnd@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-staging@lists.linux.dev, Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH 0/7] staging: gpib: randconfig build fixes
Date: Wed, 16 Oct 2024 14:33:20 +0200 [thread overview]
Message-ID: <Zw-ykGZlKNZJujAq@egonzo> (raw)
In-Reply-To: <20241016111521.1143191-1-arnd@kernel.org>
On Wed, Oct 16, 2024 at 11:15:14AM +0000, Arnd Bergmann wrote:
> From: Arnd Bergmann <arnd@arndb.de>
>
> The newly added drivers added a few build failures on my randconfig
> setup. Some of these only happen with extra warnings enabled, or with
> the pending series to allow CONFIG_HAS_IOPORT to be disabled.
>
> Arnd
>
> Arnd Bergmann (7):
> staging: gpib: add module descriptions
> staging: gpib: avoid unused const variables
> staging: gpib: pc2: avoid calling undefined dma_free()
> staging: gpib: make port I/O code conditional
> staging: gpib: add bus specific Kconfig dependencies
> staging: gpib: use proper format string in request_module
> staging: gpib: cb7210: select NEC7210 library
>
> drivers/staging/gpib/Kconfig | 18 ++++++++-
> .../gpib/agilent_82350b/agilent_82350b.c | 1 +
> .../gpib/agilent_82357a/agilent_82357a.c | 1 +
> drivers/staging/gpib/cb7210/cb7210.c | 1 +
> drivers/staging/gpib/cec/cec_gpib.c | 1 +
> drivers/staging/gpib/common/gpib_os.c | 9 +++--
> drivers/staging/gpib/eastwood/fluke_gpib.c | 1 +
> drivers/staging/gpib/eastwood/fluke_gpib.h | 8 ++--
> drivers/staging/gpib/gpio/gpib_bitbang.c | 1 +
> drivers/staging/gpib/hp_82335/hp82335.c | 1 +
> .../staging/gpib/include/nec7210_registers.h | 6 +--
> drivers/staging/gpib/include/tms9914.h | 4 +-
> .../staging/gpib/include/tnt4882_registers.h | 4 +-
> drivers/staging/gpib/ines/ines.h | 3 --
> drivers/staging/gpib/ines/ines_gpib.c | 7 +++-
> .../gpib/lpvo_usb_gpib/lpvo_usb_gpib.c | 1 +
> drivers/staging/gpib/nec7210/nec7210.c | 39 ++++++++++---------
> drivers/staging/gpib/ni_usb/ni_usb_gpib.c | 1 +
> drivers/staging/gpib/pc2/pc2_gpib.c | 5 +++
> drivers/staging/gpib/tms9914/tms9914.c | 6 +--
> drivers/staging/gpib/tnt4882/tnt4882_gpib.c | 4 +-
> drivers/staging/gpib/uapi/gpib_user.h | 20 +++++-----
> 22 files changed, 93 insertions(+), 49 deletions(-)
>
> --
> 2.39.5
>
Hi Arnd,
Thanks for this. I will test the drivers for which I have hardware
and get back to you.
-Dave
prev parent reply other threads:[~2024-10-16 12:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-16 11:15 [PATCH 0/7] staging: gpib: randconfig build fixes Arnd Bergmann
2024-10-16 11:15 ` [PATCH 1/7] staging: gpib: add module descriptions Arnd Bergmann
2024-10-16 11:15 ` [PATCH 2/7] staging: gpib: avoid unused const variables Arnd Bergmann
2024-10-16 11:15 ` [PATCH 3/7] staging: gpib: pc2: avoid calling undefined dma_free() Arnd Bergmann
2024-10-16 11:15 ` [PATCH 4/7] staging: gpib: make port I/O code conditional Arnd Bergmann
2024-11-08 19:29 ` Nathan Chancellor
2024-10-16 11:15 ` [PATCH 5/7] staging: gpib: add bus specific Kconfig dependencies Arnd Bergmann
2024-10-16 11:15 ` [PATCH 6/7] staging: gpib: use proper format string in request_module Arnd Bergmann
2024-10-16 11:15 ` [PATCH 7/7] staging: gpib: cb7210: select NEC7210 library Arnd Bergmann
2024-10-16 12:33 ` Dave Penkler [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=Zw-ykGZlKNZJujAq@egonzo \
--to=dpenkler@gmail.com \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=gregkh@linuxfoundation.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