* Randy Dunlap ([EMAIL PROTECTED]) wrote:
> Mathieu Desnoyers wrote:
> >* Randy Dunlap ([EMAIL PROTECTED]) wrote:
> >>On Mon, 24 Sep 2007 17:08:30 -0400 Mathieu Desnoyers wrote:
> >>
> >>>* Randy Dunlap ([EMAIL PROTECTED]) wrote:
> On Mon, 24 Sep 2007 11:56:35 -0700 Randy Dunlap wrote:
>
On Mon, Sep 24, 2007 at 09:31:08PM -0400, Steven Rostedt wrote:
> looking at Documentation/lguest/
>
> Oh wait, nothing to see here. Move along please.
lguest is an even bigger nightmare. It's userspace code, but we can't
move it because it pokes into non-exported headers.
-
To unsubscribe
On Mon, Sep 24, 2007 at 09:31:08PM -0400, Steven Rostedt wrote:
looking at Documentation/lguest/
Oh wait, nothing to see here. Move along please.
lguest is an even bigger nightmare. It's userspace code, but we can't
move it because it pokes into non-exported headers.
-
To unsubscribe from
* Randy Dunlap ([EMAIL PROTECTED]) wrote:
Mathieu Desnoyers wrote:
* Randy Dunlap ([EMAIL PROTECTED]) wrote:
On Mon, 24 Sep 2007 17:08:30 -0400 Mathieu Desnoyers wrote:
* Randy Dunlap ([EMAIL PROTECTED]) wrote:
On Mon, 24 Sep 2007 11:56:35 -0700 Randy Dunlap wrote:
Christoph Hellwig
Mathieu Desnoyers wrote:
* Randy Dunlap ([EMAIL PROTECTED]) wrote:
On Mon, 24 Sep 2007 17:08:30 -0400 Mathieu Desnoyers wrote:
* Randy Dunlap ([EMAIL PROTECTED]) wrote:
On Mon, 24 Sep 2007 11:56:35 -0700 Randy Dunlap wrote:
Christoph Hellwig wrote:
On Mon, Sep 24, 2007 at 11:49:15AM
* Randy Dunlap ([EMAIL PROTECTED]) wrote:
> On Mon, 24 Sep 2007 17:08:30 -0400 Mathieu Desnoyers wrote:
>
> > * Randy Dunlap ([EMAIL PROTECTED]) wrote:
> > > On Mon, 24 Sep 2007 11:56:35 -0700 Randy Dunlap wrote:
> > >
> > > > Christoph Hellwig wrote:
> > > > > On Mon, Sep 24, 2007 at 11:49:15AM
On Mon, Sep 24, 2007 at 06:50:44PM +0100, Christoph Hellwig wrote:
> On Mon, Sep 24, 2007 at 12:49:56PM -0400, Mathieu Desnoyers wrote:
> > Here is some documentation explaining what is/how to use the Linux
> > Kernel Markers.
>
> As mentioned in the tracing infrastructure thread I don't think
>
On Mon, 24 Sep 2007 17:08:30 -0400 Mathieu Desnoyers wrote:
> * Randy Dunlap ([EMAIL PROTECTED]) wrote:
> > On Mon, 24 Sep 2007 11:56:35 -0700 Randy Dunlap wrote:
> >
> > > Christoph Hellwig wrote:
> > > > On Mon, Sep 24, 2007 at 11:49:15AM -0700, Randy Dunlap wrote:
> > > >> I think that
* Randy Dunlap ([EMAIL PROTECTED]) wrote:
> On Mon, 24 Sep 2007 11:56:35 -0700 Randy Dunlap wrote:
>
> > Christoph Hellwig wrote:
> > > On Mon, Sep 24, 2007 at 11:49:15AM -0700, Randy Dunlap wrote:
> > >> I think that samples are perfectly fine for documentation and
> > >> that the trace example
On Mon, 24 Sep 2007 11:56:35 -0700 Randy Dunlap wrote:
> Christoph Hellwig wrote:
> > On Mon, Sep 24, 2007 at 11:49:15AM -0700, Randy Dunlap wrote:
> >> I think that samples are perfectly fine for documentation and
> >> that the trace example is a good example. I think that most people
> >> who
On Mon, 24 Sep 2007 20:25:04 +0100 Christoph Hellwig wrote:
> On Mon, Sep 24, 2007 at 03:18:11PM -0400, Mathieu Desnoyers wrote:
> > > putting code into Documentation is a good idea. Either of you really
> > > should start a sample/ toplevel directory for this kind of stuff
> > > including a
On Mon, Sep 24, 2007 at 03:18:11PM -0400, Mathieu Desnoyers wrote:
> > putting code into Documentation is a good idea. Either of you really
> > should start a sample/ toplevel directory for this kind of stuff
> > including a Kconfig menu etc to be able to build these samples as
> > part of an
* Christoph Hellwig ([EMAIL PROTECTED]) wrote:
> On Mon, Sep 24, 2007 at 12:49:56PM -0400, Mathieu Desnoyers wrote:
> > Here is some documentation explaining what is/how to use the Linux
> > Kernel Markers.
>
> As mentioned in the tracing infrastructure thread I don't think
> putting code into
Christoph Hellwig wrote:
On Mon, Sep 24, 2007 at 11:49:15AM -0700, Randy Dunlap wrote:
I think that samples are perfectly fine for documentation and
that the trace example is a good example. I think that most people
who need something like that would need to customize it for their
specific
On Mon, Sep 24, 2007 at 11:49:15AM -0700, Randy Dunlap wrote:
> I think that samples are perfectly fine for documentation and
> that the trace example is a good example. I think that most people
> who need something like that would need to customize it for their
> specific needs anyway.
>
> We
Christoph Hellwig wrote:
On Mon, Sep 24, 2007 at 11:23:35AM -0700, Randy Dunlap wrote:
That might be OK for this case, but sometimes it makes sense to have
README etc. about how to use the software. So you would want this
in the Documentation/ tree? That makes it harder on users.
If it's so
On Mon, Sep 24, 2007 at 11:23:35AM -0700, Randy Dunlap wrote:
> That might be OK for this case, but sometimes it makes sense to have
> README etc. about how to use the software. So you would want this
> in the Documentation/ tree? That makes it harder on users.
If it's so complex that we can't
Christoph Hellwig wrote:
On Mon, Sep 24, 2007 at 11:13:18AM -0700, Randy Dunlap wrote:
Documentation/trace/src/Makefile |7 +
Documentation/trace/src/README | 18 +
Documentation/trace/src/fork_trace.c | 119 +++
Documentation/trace/trace.txt| 164 ++
On Mon, Sep 24, 2007 at 11:13:18AM -0700, Randy Dunlap wrote:
> Documentation/trace/src/Makefile |7 +
> Documentation/trace/src/README | 18 +
> Documentation/trace/src/fork_trace.c | 119 +++
> Documentation/trace/trace.txt| 164 ++
> include/linux/trace.h
On Mon, 24 Sep 2007 19:00:41 +0100 Christoph Hellwig wrote:
> On Mon, Sep 24, 2007 at 10:56:32AM -0700, Randy Dunlap wrote:
> > I don't have a problem with a samples/ directory except (as I have
> > already pointed out) it means that people will end up having to look
> > in 2 places for the
On Mon, Sep 24, 2007 at 10:56:32AM -0700, Randy Dunlap wrote:
> I don't have a problem with a samples/ directory except (as I have
> already pointed out) it means that people will end up having to look
> in 2 places for the information that they need, i.e., both in
> samples/ and in
On Mon, 24 Sep 2007 18:50:44 +0100 Christoph Hellwig wrote:
> On Mon, Sep 24, 2007 at 12:49:56PM -0400, Mathieu Desnoyers wrote:
> > Here is some documentation explaining what is/how to use the Linux
> > Kernel Markers.
>
> As mentioned in the tracing infrastructure thread I don't think
>
On Mon, Sep 24, 2007 at 12:49:56PM -0400, Mathieu Desnoyers wrote:
> Here is some documentation explaining what is/how to use the Linux
> Kernel Markers.
As mentioned in the tracing infrastructure thread I don't think
putting code into Documentation is a good idea. Either of you really
should
On Mon, Sep 24, 2007 at 12:49:56PM -0400, Mathieu Desnoyers wrote:
Here is some documentation explaining what is/how to use the Linux
Kernel Markers.
As mentioned in the tracing infrastructure thread I don't think
putting code into Documentation is a good idea. Either of you really
should
On Mon, 24 Sep 2007 18:50:44 +0100 Christoph Hellwig wrote:
On Mon, Sep 24, 2007 at 12:49:56PM -0400, Mathieu Desnoyers wrote:
Here is some documentation explaining what is/how to use the Linux
Kernel Markers.
As mentioned in the tracing infrastructure thread I don't think
putting code
On Mon, Sep 24, 2007 at 10:56:32AM -0700, Randy Dunlap wrote:
I don't have a problem with a samples/ directory except (as I have
already pointed out) it means that people will end up having to look
in 2 places for the information that they need, i.e., both in
samples/ and in Documentation/.
On Mon, 24 Sep 2007 19:00:41 +0100 Christoph Hellwig wrote:
On Mon, Sep 24, 2007 at 10:56:32AM -0700, Randy Dunlap wrote:
I don't have a problem with a samples/ directory except (as I have
already pointed out) it means that people will end up having to look
in 2 places for the information
On Mon, Sep 24, 2007 at 11:13:18AM -0700, Randy Dunlap wrote:
Documentation/trace/src/Makefile |7 +
Documentation/trace/src/README | 18 +
Documentation/trace/src/fork_trace.c | 119 +++
Documentation/trace/trace.txt| 164 ++
include/linux/trace.h
Christoph Hellwig wrote:
On Mon, Sep 24, 2007 at 11:13:18AM -0700, Randy Dunlap wrote:
Documentation/trace/src/Makefile |7 +
Documentation/trace/src/README | 18 +
Documentation/trace/src/fork_trace.c | 119 +++
Documentation/trace/trace.txt| 164 ++
On Mon, Sep 24, 2007 at 11:23:35AM -0700, Randy Dunlap wrote:
That might be OK for this case, but sometimes it makes sense to have
README etc. about how to use the software. So you would want this
in the Documentation/ tree? That makes it harder on users.
If it's so complex that we can't
Christoph Hellwig wrote:
On Mon, Sep 24, 2007 at 11:23:35AM -0700, Randy Dunlap wrote:
That might be OK for this case, but sometimes it makes sense to have
README etc. about how to use the software. So you would want this
in the Documentation/ tree? That makes it harder on users.
If it's so
On Mon, Sep 24, 2007 at 11:49:15AM -0700, Randy Dunlap wrote:
I think that samples are perfectly fine for documentation and
that the trace example is a good example. I think that most people
who need something like that would need to customize it for their
specific needs anyway.
We don't
Christoph Hellwig wrote:
On Mon, Sep 24, 2007 at 11:49:15AM -0700, Randy Dunlap wrote:
I think that samples are perfectly fine for documentation and
that the trace example is a good example. I think that most people
who need something like that would need to customize it for their
specific
* Christoph Hellwig ([EMAIL PROTECTED]) wrote:
On Mon, Sep 24, 2007 at 12:49:56PM -0400, Mathieu Desnoyers wrote:
Here is some documentation explaining what is/how to use the Linux
Kernel Markers.
As mentioned in the tracing infrastructure thread I don't think
putting code into
On Mon, Sep 24, 2007 at 03:18:11PM -0400, Mathieu Desnoyers wrote:
putting code into Documentation is a good idea. Either of you really
should start a sample/ toplevel directory for this kind of stuff
including a Kconfig menu etc to be able to build these samples as
part of an
On Mon, 24 Sep 2007 20:25:04 +0100 Christoph Hellwig wrote:
On Mon, Sep 24, 2007 at 03:18:11PM -0400, Mathieu Desnoyers wrote:
putting code into Documentation is a good idea. Either of you really
should start a sample/ toplevel directory for this kind of stuff
including a Kconfig menu
On Mon, 24 Sep 2007 11:56:35 -0700 Randy Dunlap wrote:
Christoph Hellwig wrote:
On Mon, Sep 24, 2007 at 11:49:15AM -0700, Randy Dunlap wrote:
I think that samples are perfectly fine for documentation and
that the trace example is a good example. I think that most people
who need
* Randy Dunlap ([EMAIL PROTECTED]) wrote:
On Mon, 24 Sep 2007 11:56:35 -0700 Randy Dunlap wrote:
Christoph Hellwig wrote:
On Mon, Sep 24, 2007 at 11:49:15AM -0700, Randy Dunlap wrote:
I think that samples are perfectly fine for documentation and
that the trace example is a good
On Mon, 24 Sep 2007 17:08:30 -0400 Mathieu Desnoyers wrote:
* Randy Dunlap ([EMAIL PROTECTED]) wrote:
On Mon, 24 Sep 2007 11:56:35 -0700 Randy Dunlap wrote:
Christoph Hellwig wrote:
On Mon, Sep 24, 2007 at 11:49:15AM -0700, Randy Dunlap wrote:
I think that samples are perfectly
On Mon, Sep 24, 2007 at 06:50:44PM +0100, Christoph Hellwig wrote:
On Mon, Sep 24, 2007 at 12:49:56PM -0400, Mathieu Desnoyers wrote:
Here is some documentation explaining what is/how to use the Linux
Kernel Markers.
As mentioned in the tracing infrastructure thread I don't think
putting
* Randy Dunlap ([EMAIL PROTECTED]) wrote:
On Mon, 24 Sep 2007 17:08:30 -0400 Mathieu Desnoyers wrote:
* Randy Dunlap ([EMAIL PROTECTED]) wrote:
On Mon, 24 Sep 2007 11:56:35 -0700 Randy Dunlap wrote:
Christoph Hellwig wrote:
On Mon, Sep 24, 2007 at 11:49:15AM -0700, Randy
Mathieu Desnoyers wrote:
* Randy Dunlap ([EMAIL PROTECTED]) wrote:
On Mon, 24 Sep 2007 17:08:30 -0400 Mathieu Desnoyers wrote:
* Randy Dunlap ([EMAIL PROTECTED]) wrote:
On Mon, 24 Sep 2007 11:56:35 -0700 Randy Dunlap wrote:
Christoph Hellwig wrote:
On Mon, Sep 24, 2007 at 11:49:15AM
42 matches
Mail list logo
