Messages in this thread | | | Date | Tue, 12 Aug 2003 23:26:23 -0400 | From | Jeff Garzik <> | Subject | Re: C99 Initialisers |
| |
Randy.Dunlap wrote: > Maybe I read too much into it. It made me think of Jeff's previous > remarks about driver config and help being close to but split from > driver source code. I saw (read) it as an extension of that: > a way to package all driver information neatly close together, > but in separate files. Someone could modify the config, help, or IDs > file(s) without mucking with the driver source file(s).
You got it. I've even queried Roman Zippel about moving some of the more simple per-driver fragments in drivers/*/Makefile into drivers/*/Kconfig, so that people adding drivers only have to add one file, and patch one file. All of the driver-specific metadata stays in one place.
It would be straightforward to put the PCI IDs into Kconfig, even. We already have the parser for it, so writing the tool to generate pci_device_id C code initializers already has the backend written.
Jeff, the radical
- 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/
| |