* Re: silly [< >] and other excess
@ 2000-11-23 2:24 Andries.Brouwer
2000-11-23 14:29 ` Charles Cazabon
2000-11-23 16:14 ` [PATCH] " Peter Samuelson
0 siblings, 2 replies; 4+ messages in thread
From: Andries.Brouwer @ 2000-11-23 2:24 UTC (permalink / raw)
To: Andries.Brouwer, alan; +Cc: linux-kernel, rmk
> Thats because too many things get put on a line then.
> And because we do [<foo>] [<bar>] not [<foo>][<bar>] ?
In the good old times we had foo bar for a total of 8*(8+1) = 72
positions. Now we have [<foo>] [<bar>] which takes 8*(8+1+4) = 104
positions. If you turned this into 6 items per line instead of 8,
it would certainly improve matters a bit.
Still..
Andries
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: silly [< >] and other excess
2000-11-23 2:24 silly [< >] and other excess Andries.Brouwer
@ 2000-11-23 14:29 ` Charles Cazabon
2000-11-23 20:16 ` Tuomas Heino
2000-11-23 16:14 ` [PATCH] " Peter Samuelson
1 sibling, 1 reply; 4+ messages in thread
From: Charles Cazabon @ 2000-11-23 14:29 UTC (permalink / raw)
To: linux-kernel
Andries.Brouwer@cwi.nl <Andries.Brouwer@cwi.nl> wrote:
> > Thats because too many things get put on a line then.
> > And because we do [<foo>] [<bar>] not [<foo>][<bar>] ?
>
> In the good old times we had foo bar for a total of 8*(8+1) = 72
> positions. Now we have [<foo>] [<bar>] which takes 8*(8+1+4) = 104
> positions. If you turned this into 6 items per line instead of 8,
> it would certainly improve matters a bit.
The original poster complained the output lines were too wide for the screen
on his PC. Perhaps he should change his console mode to 132 characters wide
(via SVGATextMode or such) -- voila, no more problem, no broken kernel patches.
Charles
--
--------------------------------------------------------------
Charles Cazabon <linux@discworld.dyndns.org>
My opinions do not necessarily represent those of my employer.
--------------------------------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
^ permalink raw reply [flat|nested] 4+ messages in thread
* [PATCH] silly [< >] and other excess
2000-11-23 2:24 silly [< >] and other excess Andries.Brouwer
2000-11-23 14:29 ` Charles Cazabon
@ 2000-11-23 16:14 ` Peter Samuelson
1 sibling, 0 replies; 4+ messages in thread
From: Peter Samuelson @ 2000-11-23 16:14 UTC (permalink / raw)
To: Andries.Brouwer, kaos; +Cc: alan, linux-kernel, rmk
[Alan Cox]
> > Thats because too many things get put on a line then.
> > And because we do [<foo>] [<bar>] not [<foo>][<bar>] ?
[Andries Brouwer]
> In the good old times we had foo bar for a total of 8*(8+1) = 72
> positions. Now we have [<foo>] [<bar>] which takes 8*(8+1+4) = 104
I've got it! Put multiple addresses within one set of [< >]. ksymoops
and klogd will require a small adjustment, of course.
The following show_stack() is 8 addrs per line, 79 columns. Comments?
Peter
--- arch/i386/kernel/traps.c.orig Mon Nov 13 01:44:02 2000
+++ arch/i386/kernel/traps.c Thu Nov 23 10:10:06 2000
@@ -126,7 +126,6 @@
printk("%08lx ", *stack++);
}
- printk("\nCall Trace: ");
stack = esp;
i = 1;
module_start = VMALLOC_START;
@@ -144,12 +143,17 @@
if (((addr >= (unsigned long) &_stext) &&
(addr <= (unsigned long) &_etext)) ||
((addr >= module_start) && (addr <= module_end))) {
- if (i && ((i % 8) == 0))
- printk("\n ");
- printk("[<%08lx>] ", addr);
+ if (i==1)
+ printk("\nCall Trace: [<");
+ else if ((i % 8)==0)
+ printk(">]\n [<");
+ else
+ printk(" ");
+ printk("%08lx", addr);
i++;
}
}
+ printk(">]\n");
}
static void show_registers(struct pt_regs *regs)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: silly [< >] and other excess
2000-11-23 14:29 ` Charles Cazabon
@ 2000-11-23 20:16 ` Tuomas Heino
0 siblings, 0 replies; 4+ messages in thread
From: Tuomas Heino @ 2000-11-23 20:16 UTC (permalink / raw)
To: Charles Cazabon; +Cc: linux-kernel
On Thu, 23 Nov 2000, Charles Cazabon wrote:
> Andries.Brouwer@cwi.nl <Andries.Brouwer@cwi.nl> wrote:
> > > Thats because too many things get put on a line then.
> > > And because we do [<foo>] [<bar>] not [<foo>][<bar>] ?
> >
> > In the good old times we had foo bar for a total of 8*(8+1) = 72
> > positions. Now we have [<foo>] [<bar>] which takes 8*(8+1+4) = 104
> > positions. If you turned this into 6 items per line instead of 8,
> > it would certainly improve matters a bit.
>
> The original poster complained the output lines were too wide for the screen
> on his PC. Perhaps he should change his console mode to 132 characters wide
> (via SVGATextMode or such) -- voila, no more problem, no broken kernel patches.
Well that 72 characters is also known as the "safe" email line length...
... and besides some people still use the old VT330s and alike ;)
But in practice even those 79 chars would be better than 104.
--
No .sig here... especially no 128x48 .sig here - nor 132xYuch...
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2000-11-23 20:47 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2000-11-23 2:24 silly [< >] and other excess Andries.Brouwer
2000-11-23 14:29 ` Charles Cazabon
2000-11-23 20:16 ` Tuomas Heino
2000-11-23 16:14 ` [PATCH] " Peter Samuelson
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®