From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] scsi: advansys needs ISA dma api for ISA support
Date: Fri, 16 Oct 2015 16:19:18 +0200 [thread overview]
Message-ID: <5461074.f3cLgYkzKJ@wuerfel> (raw)
In-Reply-To: <1445003624.2191.2.camel@HansenPartnership.com>
On Friday 16 October 2015 06:53:44 James Bottomley wrote:
> >
> > Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> >
> > diff --git a/drivers/scsi/Kconfig b/drivers/scsi/Kconfig
> > index d2f480b04a52..1d8b8257773d 100644
> > --- a/drivers/scsi/Kconfig
> > +++ b/drivers/scsi/Kconfig
> > @@ -498,7 +498,7 @@ config SCSI_DPT_I2O
> > config SCSI_ADVANSYS
> > tristate "AdvanSys SCSI support"
> > depends on SCSI
> > - depends on ISA || EISA || PCI
> > + depends on (ISA && ISA_DMA_API) || EISA || PCI
>
> I thought the desire was to avoid a compile failure when ISA && !
> ISA_DMA_API? Won't this one fail if ISA is defined with either EISA or
> PCI and !ISA_DMA_API?
I thought I had it ruled out, but now I've actually found a combination:
we can build an ARM kernel that supports two ancient machines, and one
of them supports ISA (but not ISA_DMA_API), while the other one supports
PCI. I had looked through several thousand randconfig builds and not
found this combination together with advansys, but I guess that is
because those were mostly old builds from the times when there was
a dependency on VIRT_TO_BUS that this platform doesn't have.
So screw this one and go back to the original patch.
Arnd
next prev parent reply other threads:[~2015-10-16 14:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-16 12:13 [PATCH v2] scsi: advansys needs ISA dma api for ISA support Arnd Bergmann
2015-10-16 12:16 ` Hannes Reinecke
2015-10-16 13:53 ` James Bottomley
2015-10-16 14:19 ` Arnd Bergmann [this message]
2015-10-16 14:26 ` James Bottomley
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=5461074.f3cLgYkzKJ@wuerfel \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.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