> > This means that it would be compiled into the kernel several times.
> > You should add it to the core scsi code and _not_ declare it static.
>
> I considered doing it this way. As I saw it, it's a tradeoff between
> including the code even if none of the drivers in question are
> configured in, or compiling it multiple times if several of them are. I
> guess there's also the possibility of an ifdef so that it will be
> compiled if at least one of drivers is configured in.
>
> However, in light of other email in this thread, it looks like maybe the
> table can go altogether, so hopefully this question is now moot.
I think this will not be the case. Alan is right.
Compatibilty should not be lightly broken.
Given that most new drivers will probably need a direction I still think that
you should add it to the scsi core. You don't increase the core code by much,
but you make some loadable modules consume a page less.
Regards
Oliver
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
