Messages in this thread | | | Date | Fri, 9 Aug 2002 12:21:30 +0200 (CEST) | From | Roman Zippel <> | Subject | Re: 64bit clean drivers was Re: Linux 2.4.20-pre1 |
| |
Hi,
On Thu, 8 Aug 2002, Peter Samuelson wrote:
> > Boolean is simple, what about tristate symbols? How does it modify > > the input range? > > !y == n > !m == n > !n == y > > To me these are the only semantics that make any sense. Certainly if > it goes in the kernel it needs to be added to config-language.txt.
I would define !m as m, e.g. it would allow
dep_tristate "" CONFIG_OLD !$CONFIG_NEW dep_tristate "" CONFIG_NEW !$CONFIG_OLD
This means only a single driver could be build into the kernel, but both could be compiled as module. If we had real expression there, your semantics could easily be described as $CONFIG!=n, but it wouldn't be possible to describe my semantics.
bye, Roman
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |