mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Arnd Bergmann" <arnd@arndb.de>
To: "Pascal Hambourg" <pascal@plouf.fr.eu.org>,
	"Martin K. Petersen" <martin.petersen@oracle.com>
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Bartlomiej Zolnierkiewicz" <bzolnier@gmail.com>
Subject: Re: [PATCH] scsi: advansys: disallow ISA-only build
Date: Thu, 20 Apr 2023 16:25:50 +0200	[thread overview]
Message-ID: <d018f78d-13d0-4d13-90c5-9b33bd121f51@app.fastmail.com> (raw)
In-Reply-To: <e6958e2e-47bc-685b-f585-a88d29173f58@plouf.fr.eu.org>

On Thu, Apr 20, 2023, at 14:40, Pascal Hambourg wrote:
> Hello Arnd, Peter,
>
> Arnd Bergmann wrote:
>> The ISA support for this driver was removed a while ago,
>> but the Kconfig dependencies still need an update to require
>> EISA or PCI.
>
> A month ago I posted to linux-scsi about the module failing to to init 
> if ISA support is disabled in the kernel config (copy attached), but 
> have not received any answer so far. Any thoughts ?
> Attachments:
> * [Bug report] scsi: advansys: module init fails if ISA_BUS_API is not set.eml
[https://lore.kernel.org/all/5b30b2b2-c47a-da1e-8106-025c914faebd@plouf.fr.eu.org]

Thanks for getting back to me on that. It looks like my patch
was incorrect after all, and only the ISA_DMA_API should have
been removed, as it's now impossible to build a VLB-only version
of the driver.

I think the two ways we can address this are:

- your approach c), which makes it behave the same as the aha1542.c and
  g_NCR5380.c drivers, plus a Kconfig fix to add back ISA_BUS_API
  as a possible alternative to PCI and EISA (thus fixing my patch).

- your approach d), removing VLB support for this driver. I tried to
  find other VLB drivers and the only ones I see remaining in linux-6.3
  are drivers/ata/pata_legacy and drivers/net/ethernet/amd/pcnet32.c.
  Bartlomiej Zolnierkiewicz (added to Cc) is the only one that I can
  see having actually touched VLB drivers at all in over a decade, he
  might know more.

      Arnd

       reply	other threads:[~2023-04-20 14:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5b30b2b2-c47a-da1e-8106-025c914faebd@plouf.fr.eu.org>
     [not found] ` <e6958e2e-47bc-685b-f585-a88d29173f58@plouf.fr.eu.org>
2023-04-20 14:25   ` Arnd Bergmann [this message]
2023-04-17 20:51 Arnd Bergmann
2023-04-19  3:12 ` Martin K. Petersen

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=d018f78d-13d0-4d13-90c5-9b33bd121f51@app.fastmail.com \
    --to=arnd@arndb.de \
    --cc=bzolnier@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=pascal@plouf.fr.eu.org \
    /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®