[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0dc901d4f37a$52733a70$f759af50$@d-silva.org>
Date: Mon, 15 Apr 2019 20:59:36 +1000
From: "Alastair D'Silva" <alastair@...ilva.org>
To: "'David Laight'" <David.Laight@...LAB.COM>,
"'Petr Mladek'" <pmladek@...e.com>
Cc: "'Jani Nikula'" <jani.nikula@...ux.intel.com>,
"'Joonas Lahtinen'" <joonas.lahtinen@...ux.intel.com>,
"'Rodrigo Vivi'" <rodrigo.vivi@...el.com>,
"'David Airlie'" <airlied@...ux.ie>,
"'Daniel Vetter'" <daniel@...ll.ch>,
"'Karsten Keil'" <isdn@...ux-pingi.de>,
"'Jassi Brar'" <jassisinghbrar@...il.com>,
"'Tom Lendacky'" <thomas.lendacky@....com>,
"'David S. Miller'" <davem@...emloft.net>,
"'Jose Abreu'" <Jose.Abreu@...opsys.com>,
"'Kalle Valo'" <kvalo@...eaurora.org>,
"'Stanislaw Gruszka'" <sgruszka@...hat.com>,
"'Benson Leung'" <bleung@...omium.org>,
"'Enric Balletbo i Serra'" <enric.balletbo@...labora.com>,
"'James E.J. Bottomley'" <jejb@...ux.ibm.com>,
"'Martin K. Petersen'" <martin.petersen@...cle.com>,
"'Greg Kroah-Hartman'" <gregkh@...uxfoundation.org>,
"'Alexander Viro'" <viro@...iv.linux.org.uk>,
"'Sergey Senozhatsky'" <sergey.senozhatsky@...il.com>,
"'Steven Rostedt'" <rostedt@...dmis.org>,
"'Andrew Morton'" <akpm@...ux-foundation.org>,
<intel-gfx@...ts.freedesktop.org>,
<dri-devel@...ts.freedesktop.org>, <linux-kernel@...r.kernel.org>,
<netdev@...r.kernel.org>, <ath10k@...ts.infradead.org>,
<linux-wireless@...r.kernel.org>, <linux-scsi@...r.kernel.org>,
<linux-fbdev@...r.kernel.org>, <devel@...verdev.osuosl.org>,
<linux-fsdevel@...r.kernel.org>
Subject: RE: [PATCH 1/4] lib/hexdump.c: Allow 64 bytes per line
> From: Alastair D'Silva
> > Sent: 15 April 2019 11:29
> ...
> > I do, and I believe the choice of the output length should be in the
> > hands of the caller.
> >
> > On further thought, it would make more sense to remove the hardcoded
> > list of sizes and just enforce a power of 2. The function shouldn't
> > dictate what the caller can and can't do beyond the technical limits of it's
> implementation.
>
> Why powers of two?
> You may want the length to match sizeof (struct foo).
> You might even want the address increment to be larger that the number of
> lines dumped.
Good point, the base requirement is that it should be a multiple of groupsize.
--
Alastair D'Silva mob: 0423 762 819
skype: alastair_dsilva msn: alastair@...ilva.org
blog: http://alastair.d-silva.org Twitter: @EvilDeece
Powered by blists - more mailing lists