From: Tommaso Perondi <perondi.tommaso@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: "Tommaso Perondi" <perondi.tommaso@gmail.com>,
dpenkler@gmail.com, linux-kernel@vger.kernel.org,
"Josef Bacik" <josef@toxicpanda.com>, stable <stable@kernel.org>,
"Dominik Karol Piątkowski"
<dominik.karol.piatkowski@protonmail.com>,
"Uwe Kleine-König (The Capable Hub)"
<u.kleine-koenig@baylibre.com>
Subject: Re: [PATCH] gpib: tnt4882: set iobase for the ISA and PCMCIA boards
Date: Wed, 18 Nov 2026 17:51:40 +0100 [thread overview]
Message-ID: <20261118165140.1481402-1-perondi.tommaso@gmail.com> (raw)
In-Reply-To: <2026102704-deletion-handcart-ee29@gregkh>
On Tue, Oct 27, 2026 at 05:29:03PM +0100, Greg Kroah-Hartman wrote:
> - Both detach functions call release_region() only if iobase is set. The
> region is never released, so the board cannot be put online a second
> time: request_region() fails with -EBUSY until the next boot.
Hi Greg, Josef, thanks for the fix.
I applied this patch and tested it on a National Instruments
AT-GPIB/TNT (ISA) board. REN is asserted again and I can take the
board offline and back online without getting -EBUSY.
I don't have a GPIB-PCMCIA card, so I could not test the PCMCIA part
(including the new iosize field).
There is no gpib list, so you may have missed it: I posted this fix in
August as a two-patch series (ISA and PCMCIA). I won't resend
mine. Feel free to add the Link: below to the commit if you think it's
useful for the history, or just drop it.
Link: https://lore.kernel.org/all/20260815195757.2001555-1-perondi.tommaso@gmail.com/
Tested-by: Tommaso Perondi <perondi.tommaso@gmail.com> # ISA only
Tommaso
prev parent reply other threads:[~2026-11-18 16:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 16:29 Greg Kroah-Hartman
2026-11-18 16:51 ` Tommaso Perondi [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=20261118165140.1481402-1-perondi.tommaso@gmail.com \
--to=perondi.tommaso@gmail.com \
--cc=dominik.karol.piatkowski@protonmail.com \
--cc=dpenkler@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=josef@toxicpanda.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@kernel.org \
--cc=u.kleine-koenig@baylibre.com \
/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®