Messages in this thread | | | Date | Sat, 23 Jun 2007 15:55:05 +0100 | From | Alan Cox <> | Subject | Re: [patch 03/10] Allow userspace applications to use marker.h to parse the markers section in the kernel binary. |
| |
On Sat, 23 Jun 2007 11:06:00 +0100 Christoph Hellwig <hch@infradead.org> wrote:
> On Sat, Jun 23, 2007 at 10:49:05AM +0100, Alan Cox wrote: > > The system to create the dynamic modules could certainly be in-tree but to > > argue that code dynamically created should be "in tree" already is a > > bit silly really isn't it ? > > I never argued that. Creating them intree is equivalent to having the > generated modules in tree for all purposes related to interface stability.
So if all the applications using markers are shoved into the kernel source tree you are happy, and if they are distributed elsewhere you are not ?
Or do you want a single controlled 'with the kernel' tool for doing the outputting which alone has close links with the kernel (ie modinfo --dump-markers) or similar ? - 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/
| |