From: Joe Perches <joe@perches.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Adrian Remonda <adrianremonda@gmail.com>,
Mark Brown <broonie@kernel.org>,
corbet@lwn.net, linux-spi@vger.kernel.org,
Linux Documentation List <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/4] Cleaned hexadecimal dump
Date: Sun, 08 Mar 2015 09:20:00 -0700 [thread overview]
Message-ID: <1425831600.16901.30.camel@perches.com> (raw)
In-Reply-To: <CAHp75VcaMDqHMwQcV+p5_KjDviEr97m4e=GFVXkXLgO4pkvmjw@mail.gmail.com>
On Sun, 2015-03-08 at 12:53 +0200, Andy Shevchenko wrote:
> On Sun, Mar 8, 2015 at 4:22 AM, Joe Perches <joe@perches.com> wrote:
> > On Sat, 2015-03-07 at 12:56 -0500, Adrian Remonda wrote:
>
> >> +static void hexDump(const void *src, size_t length, size_t bLine, char *prefix)
> > Is there something necessary that print_hex_dump can't do?
> As far as I can see the tool is running in user space.
OK, I skipped over that bit. Nevermind.
> Do we have
> possibility to use print_hex_dump() in user space?
No.
next prev parent reply other threads:[~2015-03-08 16:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-07 17:56 [PATCH 0/4] spi: spidev_test: Added functionalities Adrian Remonda
2015-03-07 17:56 ` [PATCH 1/4] Cleaned hexadecimal dump Adrian Remonda
2015-03-07 17:56 ` [PATCH 2/4] Added verbose output Adrian Remonda
2015-03-07 17:56 ` [PATCH 3/4] Added input buffer from the terminal Adrian Remonda
2015-03-07 17:56 ` [PATCH 4/4] Moved spidev_tools.c to tools/spi Adrian Remonda
2015-03-09 18:38 ` [PATCH 3/4] Added input buffer from the terminal Mark Brown
2015-03-08 2:22 ` [PATCH 1/4] Cleaned hexadecimal dump Joe Perches
2015-03-08 10:53 ` Andy Shevchenko
2015-03-08 16:20 ` Joe Perches [this message]
[not found] ` <1425750995-18176-2-git-send-email-adrianremonda-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-03-09 13:51 ` Geert Uytterhoeven
2015-03-09 18:40 ` Mark Brown
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=1425831600.16901.30.camel@perches.com \
--to=joe@perches.com \
--cc=adrianremonda@gmail.com \
--cc=andy.shevchenko@gmail.com \
--cc=broonie@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).