[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.00.1710202245400.3886@tp.orcam.me.uk>
Date: Fri, 20 Oct 2017 22:46:44 +0100
From: "Maciej W. Rozycki" <macro@...s.com>
To: Joe Perches <joe@...ches.com>
CC: Aleksandar Markovic <aleksandar.markovic@...rk.com>,
<linux-mips@...ux-mips.org>,
Dragan Cecavac <dragan.cecavac@...s.com>,
Aleksandar Markovic <aleksandar.markovic@...s.com>,
Douglas Leung <douglas.leung@...s.com>,
Goran Ferenc <goran.ferenc@...s.com>,
James Hogan <james.hogan@...s.com>,
James Hogan <jhogan@...nel.org>,
<linux-kernel@...r.kernel.org>,
"Maciej W. Rozycki" <macro@...ux-mips.org>,
Miodrag Dinic <miodrag.dinic@...s.com>,
Paul Burton <paul.burton@...tec.com>,
Paul Burton <paul.burton@...s.com>,
Petar Jovanovic <petar.jovanovic@...s.com>,
Raghu Gandham <raghu.gandham@...s.com>,
Ralf Baechle <ralf@...ux-mips.org>
Subject: Re: [PATCH] MIPS: kernel: proc: Remove spurious white space in
cpuinfo
On Fri, 20 Oct 2017, Joe Perches wrote:
> > > That's somewhat unpleasant code as it formats a fmt string
> > > and the compiler can not verify fmt and args.
> > >
> > > Perhaps something like the below is preferable:
> >
> > Hmm, what problem exactly are you trying to solve with code that has
> > worked just fine for 16 years now?
>
> The compiler cannot verify fmt and args.
You have stated that already. Why is that a problem?
Maciej
Powered by blists - more mailing lists