Messages in this thread | | | Date | Sun, 7 Dec 2008 10:16:26 +1100 | From | Nick Andrew <> | Subject | Re: [RFC] Recursive printk |
| |
On Sat, Dec 06, 2008 at 01:11:33AM -0800, Joe Perches wrote: > I think the question is how to output messages that use > multiple calls to printk so they are not interleaved.
This is certainly needed e.g. for code which outputs line fragments and expects full lines in the log, such as hex dumps. But its arguable that that code should use its own buffer to format lines, then send only complete lines to printk.
> Giving up printf argument verification seems too high a > price to pay for the benefit of recursion.
I agree completely. I was hoping somebody could tell me how to include '%v' in gcc's acceptable list, but it seems impossible. The alternative then is to use '%pV%s' which gcc _should_ like (I haven't tested it, but it seems reasonable) and reverse the order of the fmt and args in the function call arguments.
Nick.
| |