From: Frederic Weisbecker <fweisbec@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>,
Lai Jiangshan <laijs@cn.fujitsu.com>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH][RFC] vsprintf: unify the format decoding layer for its 3 users
Date: Sat, 28 Feb 2009 18:18:39 +0100 [thread overview]
Message-ID: <20090228171838.GA5821@nowhere> (raw)
In-Reply-To: <alpine.LFD.2.00.0902280845580.3111@localhost.localdomain>
On Sat, Feb 28, 2009 at 08:54:15AM -0800, Linus Torvalds wrote:
>
>
> On Sat, 28 Feb 2009, Frederic Weisbecker wrote:
> >
> > You're right, that's much proper.
> > See the V2 below:
>
> Good. This looks better.
>
> One final (?) nit:
>
> > + default: {
> > + enum format_type type = spec.type;
> > +
> > + if (type == FORMAT_TYPE_LONG_LONG)
> > + num = va_arg(args, long long);
> > + else if (type == FORMAT_TYPE_ULONG)
> > + num = va_arg(args, unsigned long);
> > + else if (type == FORMAT_TYPE_LONG)
> > + num = va_arg(args, unsigned long);
> > + else if (type == FORMAT_TYPE_SIZE_T)
> > + num = va_arg(args, size_t);
> > + else if (type == FORMAT_TYPE_PTRDIFF)
> > + num = va_arg(args, ptrdiff_t);
> > + else if (type == FORMAT_TYPE_USHORT)
> > + num = (unsigned short) va_arg(args, int);
> > + else if (type == FORMAT_TYPE_SHORT)
> > + num = (short) va_arg(args, int);
> > + else if (type == FORMAT_TYPE_UINT)
> > + num = va_arg(args, unsigned int);
> > + else
> > + num = va_arg(args, unsigned int);
> > +
> > + str = number(str, end, num, spec.base,
> > + spec.field_width, spec.precision, spec.flags);
>
> You've got three copes of these (in the three different users), and that
> just looks horrid. I see why you did it, but even something like
>
> case FORMAT_TYPE_LONG_LONG:
> num = va_arg(args, long long);
> goto handle_number;
> case FORMAT_TYPE_ULONG:
> ...
> case FORMAT_TYPE_INT:
> num = va_arg(args, int);
> handle_number:
> str = number(str, end, num, &spec);
> break;
>
> would be better.
>
> And yes, please do pass in "spec" to the "number()/pointer()/string()"
> routines instead of exploding it into the individual numbers. When
> cleaning up, let's just do it properly..
>
> Linus
Ok, I'm addressing your comments and those from Ingo, then I will rebase
the whole patchset (with the ftrace_bprintk related things) against latest
-tip and resend it.
Thanks!
prev parent reply other threads:[~2009-02-28 17:18 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-24 5:17 [PATCH 1/3] add binary printf Frederic Weisbecker
2009-02-26 13:02 ` Ingo Molnar
2009-02-26 17:05 ` Frederic Weisbecker
2009-02-26 17:43 ` Ingo Molnar
2009-02-26 17:45 ` Frederic Weisbecker
2009-02-26 17:52 ` Ingo Molnar
2009-02-26 18:34 ` Frederic Weisbecker
2009-02-26 18:45 ` Ingo Molnar
2009-02-26 18:52 ` Frederic Weisbecker
2009-02-26 18:56 ` Ingo Molnar
2009-02-26 19:05 ` Frederic Weisbecker
2009-02-27 6:19 ` [PATCH][RFC] vsprintf: unify the format decoding layer for its 3 users Frederic Weisbecker
2009-02-27 6:46 ` Andrew Morton
2009-02-27 7:12 ` Frederic Weisbecker
2009-02-27 7:39 ` Andrew Morton
2009-02-27 8:32 ` Ingo Molnar
2009-02-27 8:45 ` Andrew Morton
2009-02-27 9:35 ` Ingo Molnar
2009-02-27 8:20 ` Ingo Molnar
2009-02-27 8:33 ` Andrew Morton
2009-02-27 15:03 ` Steven Rostedt
2009-02-28 0:30 ` Linus Torvalds
2009-02-28 0:39 ` Linus Torvalds
2009-02-28 8:11 ` Frederic Weisbecker
2009-02-28 9:13 ` Ingo Molnar
2009-02-28 19:45 ` [PATCH 1/5] add binary printf Frederic Weisbecker
2009-02-28 20:16 ` [PATCH 2/5] ftrace: infrastructure for supporting binary record Frederic Weisbecker
2009-03-02 16:27 ` Steven Rostedt
2009-03-02 17:39 ` Frédéric Weisbecker
2009-02-28 21:30 ` [PATCH 3/5] ftrace: add ftrace_bprintk() Frederic Weisbecker
2009-03-02 16:34 ` Steven Rostedt
2009-03-02 17:45 ` Frédéric Weisbecker
2009-03-02 17:53 ` Steven Rostedt
2009-03-02 18:06 ` Frédéric Weisbecker
2009-03-02 18:23 ` Steven Rostedt
2009-03-02 18:55 ` Frédéric Weisbecker
2009-02-28 22:16 ` [PATCH 4/5] tracing/core: drop the old ftrace_printk implementation in favour of ftrace_bprintk Frederic Weisbecker
2009-03-02 16:37 ` Steven Rostedt
2009-03-02 17:47 ` Frédéric Weisbecker
2009-02-28 23:11 ` [PATCH][RFC] vsprintf: unify the format decoding layer for its 3 users Frederic Weisbecker
2009-03-01 2:34 ` [PATCH 5/5 v3] " Frederic Weisbecker
2009-03-01 3:31 ` [PATCH 0/5] Binary ftrace_printk Frederic Weisbecker
2009-02-28 16:54 ` [PATCH][RFC] vsprintf: unify the format decoding layer for its 3 users Linus Torvalds
2009-02-28 17:18 ` Frederic Weisbecker [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090228171838.GA5821@nowhere \
--to=fweisbec@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox