Re: [PATCH v2] doc/oops-tracing: add Code: decode info

2007-06-22 Thread Andi Kleen
> Why 3 times? Why not just (1) everything before marker and > (2) everything at and after marker? 2 times would probably work too, i was just thinking of a marker around it; but you're right just before would be also ok. > > - It won't handle multiline Code:s which i386 likes to generate now I

Re: [PATCH v2] doc/oops-tracing: add Code: decode info

2007-06-22 Thread Randy Dunlap
On Fri, 22 Jun 2007 19:23:02 +0200 Andi Kleen wrote: > On Friday 22 June 2007 18:44, Randy Dunlap wrote: > > On Fri, 22 Jun 2007 16:26:39 +0200 Andi Kleen wrote: > > > On Friday 22 June 2007 07:51:08 Randy Dunlap wrote: > > > > From: Randy Dunlap <[EMAIL PROTECTED]> > > > > > > > > Add info that t

Re: [PATCH v2] doc/oops-tracing: add Code: decode info

2007-06-22 Thread Andi Kleen
On Friday 22 June 2007 18:44, Randy Dunlap wrote: > On Fri, 22 Jun 2007 16:26:39 +0200 Andi Kleen wrote: > > On Friday 22 June 2007 07:51:08 Randy Dunlap wrote: > > > From: Randy Dunlap <[EMAIL PROTECTED]> > > > > > > Add info that the Code: bytes line contains or (wxyz) in some > > > architecture

[PATCH v2] doc/oops-tracing: add Code: decode info

2007-06-22 Thread Randy Dunlap
On Fri, 22 Jun 2007 16:26:39 +0200 Andi Kleen wrote: > On Friday 22 June 2007 07:51:08 Randy Dunlap wrote: > > From: Randy Dunlap <[EMAIL PROTECTED]> > > > > Add info that the Code: bytes line contains or (wxyz) in some > > architecture oops reports and what that means. > > > > Add URL for a sc