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 <[email protected]> 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 [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • [patch 00/10] Linux Kernel Markers for 2.6.21-mm2
    • From: Mathieu Desnoyers <[email protected]>
  • [patch 03/10] Allow userspace applications to use marker.h to parse the markers section in the kernel binary.
    • From: Mathieu Desnoyers <[email protected]>
  • Re: [patch 03/10] Allow userspace applications to use marker.h to parse the markers section in the kernel binary.
    • From: Christoph Hellwig <[email protected]>
  • Re: [patch 03/10] Allow userspace applications to use marker.h to parse the markers section in the kernel binary.
    • From: David Smith <[email protected]>
  • Re: [patch 03/10] Allow userspace applications to use marker.h to parse the markers section in the kernel binary.
    • From: Christoph Hellwig <[email protected]>
  • Re: [patch 03/10] Allow userspace applications to use marker.h to parse the markers section in the kernel binary.
    • From: Alan Cox <[email protected]>
  • Re: [patch 03/10] Allow userspace applications to use marker.h to parse the markers section in the kernel binary.
    • From: Christoph Hellwig <[email protected]>
  • Re: [patch 03/10] Allow userspace applications to use marker.h to parse the markers section in the kernel binary.
    • From: Alan Cox <[email protected]>
  • Re: [patch 03/10] Allow userspace applications to use marker.h to parse the markers section in the kernel binary.
    • From: Christoph Hellwig <[email protected]>

• Prev by Date: Re: NAK (bashizm in the /bin/sh script): [PATCH v3] doc/oops-tracing: add Code: decode info
• Next by Date: Re: 2.6.21.4: possible circular locking dependency detected
• Previous by thread: Re: [patch 03/10] Allow userspace applications to use marker.h to parse the markers section in the kernel binary.
• Next by thread: [patch 09/10] Linux Kernel Markers - Use EXTRA_RWDATA in architectures
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]