[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20161024131311.ttwr2bblphg6vd2b@thunk.org>
Date: Mon, 24 Oct 2016 09:13:11 -0400
From: Theodore Ts'o <tytso@....edu>
To: SF Markus Elfring <elfring@...rs.sourceforge.net>
Cc: linux-mips@...ux-mips.org,
Andrea Gelmini <andrea.gelmini@...ma.net>,
Andrew Morton <akpm@...ux-foundation.org>,
Leonid Yegoshin <Leonid.Yegoshin@...tec.com>,
Masahiro Yamada <yamada.masahiro@...ionext.com>,
Matt Redfearn <matt.redfearn@...tec.com>,
Paul Burton <paul.burton@...tec.com>,
Paul Gortmaker <paul.gortmaker@...driver.com>,
Ralf Bächle <ralf@...ux-mips.org>,
Zubair Lutfullah Kakakhel <Zubair.Kakakhel@...tec.com>,
LKML <linux-kernel@...r.kernel.org>,
kernel-janitors@...r.kernel.org
Subject: Re: [PATCH 1/4] MIPS/kernel/r2-to-r6-emul: Use seq_puts() in
mipsr2_stats_show()
On Mon, Oct 24, 2016 at 02:27:55PM +0200, SF Markus Elfring wrote:
>
> A string which did not contain a data format specification should be put
> into a sequence.
This is not a correct description of what you are doing. A better
description would be to say:
"Use seq_put[sc]() instead of seq_printf() since the string does not
contain a data format specifier". You should fix this in all the
patches. Please also note this is really pointless patch, since
reading from /proc isn't done in a tight loop, and even if it were,
the use of vsprintf is the tiniest part of the overhead. It otherwise
reduces the text space or the number of lines of code....
- Ted
Powered by blists - more mailing lists