[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1404940868.932.168.camel@joe-AO725>
Date: Wed, 09 Jul 2014 14:21:08 -0700
From: Joe Perches <joe@...ches.com>
To: Marek Vasut <marex@...x.de>
Cc: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Tadeusz Struk <tadeusz.struk@...el.com>,
Herbert Xu <herbert@...dor.apana.org.au>,
Mauro Carvalho Chehab <m.chehab@...sung.com>,
Helge Deller <deller@....de>,
Ingo Tuchscherer <ingo.tuchscherer@...ibm.com>,
linux390@...ibm.com, Alexander Viro <viro@...iv.linux.org.uk>,
qat-linux@...el.com, linux-crypto@...r.kernel.org,
linux-media@...r.kernel.org, linux-s390@...r.kernel.org,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1 1/5] seq_file: provide an analogue of print_hex_dump()
On Wed, 2014-07-09 at 22:39 +0200, Marek Vasut wrote:
> The above function looks like almost verbatim copy of print_hex_dump(). The only
> difference I can spot is that it's calling seq_printf() instead of printk(). Can
> you not instead generalize print_hex_dump() and based on it's invocation, make
> it call either seq_printf() or printk() ?
How do you propose doing that given any seq_<foo> call
requires a struct seq_file * and print_hex_dump needs
a KERN_<LEVEL>.
Is there an actual value to it?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists