public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Penkler <dpenkler@gmail.com>
To: gregkh@linuxfoundation.org, linux-staging@lists.linux.dev,
	linux-kernel@vger.kernel.org
Cc: Dave Penkler <dpenkler@gmail.com>
Subject: [PATCH 0/3] staging: gpib: Fix CONFIG_GPIB_HP82341 build failure
Date: Fri, 24 Jan 2025 11:58:57 +0100	[thread overview]
Message-ID: <20250124105900.27592-1-dpenkler@gmail.com> (raw)

The driver was causing a build failure when comiled as a module
because the isapnp_read_byte symbol was undefined.

Patch 1 fixes a compile error introduced by an intervening patch
Patch 2 exports the isapnp_read_byte symbol for modules
Patch 3 removes the dependency on BROKEN in Kconfig

Dave Penkler (3):
  staging: gpib: Fix pr_err format warning
  pnp: isapnp: Export isapnp_read_byte again
  staging: gpib: Remove depends on BROKEN

 drivers/pnp/isapnp/core.c                | 1 +
 drivers/staging/gpib/Kconfig             | 1 -
 drivers/staging/gpib/hp_82341/hp_82341.c | 2 +-
 3 files changed, 2 insertions(+), 2 deletions(-)

-- 
2.47.1


             reply	other threads:[~2025-01-24 10:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-24 10:58 Dave Penkler [this message]
2025-01-24 10:58 ` [PATCH 1/3] staging: gpib: Fix pr_err format warning Dave Penkler
2025-01-24 10:58 ` [PATCH 2/3] pnp: isapnp: Export isapnp_read_byte again Dave Penkler
2025-01-24 10:59 ` [PATCH 3/3] staging: gpib: Remove depends on BROKEN Dave Penkler
2025-01-25 11:39   ` kernel test robot
2025-01-25 14:16   ` kernel test robot
2025-01-26 18:13     ` Dave Penkler
2025-01-25 14:47   ` kernel test robot
2025-01-26 18:18     ` Dave Penkler

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=20250124105900.27592-1-dpenkler@gmail.com \
    --to=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