Re: Aic7xxx v6.2.22 and Aic79xx v1.3.0Alpha2 Released

[Christoph Hellwig <hch@infradead.org>]

On Wed, Dec 11, 2002 at 10:31:05AM -0700, Justin T. Gibbs wrote:
> Okay.  Sine the choice directive is now gone, is there a compelling reason
> to put the "old" aic7xxx driver Kconfig directives in the same Kconfig
> file as the new driver?

I wanted to have it just below the other one.

> It is kind of nice to have the separation since
> Adaptec cannot support the old driver.

Well, it usually just works (TM) :)  But I don't really see a relation
between Kconfig entries and what's supported by whom.  The MAINTAINERS
file in the toplevel directory is the only place where certain drivers/
subsystems are claimed supported.

I also take it that you were also
> unable to make the choice directive do the right thing?  That was the
> original reason for removing the "old driver" Kconfig directives.  The
> way your patch stands now, I don't believe there is anything to prevent
> both drivers from being compiled statically into the kernel.  If so, the
> resulting kernel will not boot.

Yupp, it currently crashes when I have both compiled in.  Dough, any chance
you could fix that?  A PCI driver is not supposed to stop over already
claimed device.
I'll try to find out how to get the old depency for both not beeing allowed
to be compiled in into the new Kconfig scheme until then.