From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Paul Fox <pgf@laptop.org>, Darren Hart <dvhart@infradead.org>
Cc: linux-kernel@vger.kernel.org,
Andres Salomon <dilinger@queued.net>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH v1] OLPC: use %*ph specifier instead of passing direct values
Date: Wed, 30 Sep 2015 17:59:44 +0300 [thread overview]
Message-ID: <1443625184.8361.310.camel@linux.intel.com> (raw)
In-Reply-To: <20141229143210.C9C685180445@grass.foxharp.boston.ma.us>
On Mon, 2014-12-29 at 09:32 -0500, Paul Fox wrote:
> change looks okay to me.
> Acked-by: Paul Fox <pgf@laptop.org>
>
Darren, maybe you can apply this one? Seems OLPC is x86-based.
> paul
>
> andy wrote:
> > The %*ph specifier allows to dump small buffers in hex format.
> Let's use it
> > instead of passing direct values via stack.
> >
> > Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> > ---
> > drivers/platform/olpc/olpc-ec.c | 13 +++++--------
> > 1 file changed, 5 insertions(+), 8 deletions(-)
> >
> > diff --git a/drivers/platform/olpc/olpc-ec.c
> b/drivers/platform/olpc/olpc-ec.c
> > index f911952..f99b183 100644
> > --- a/drivers/platform/olpc/olpc-ec.c
> > +++ b/drivers/platform/olpc/olpc-ec.c
> > @@ -192,18 +192,15 @@ static ssize_t ec_dbgfs_cmd_write(struct
> file *file, const char __user *buf,
> > for (i = 0; i <= ec_cmd_bytes; i++)
> > ec_cmd[i] = ec_cmd_int[i];
> >
> > - pr_debug("olpc-ec: debugfs cmd 0x%02x with %d args %02x %02x
> %02x %02x %02x, want %d returns\n",
> > - ec_cmd[0], ec_cmd_bytes, ec_cmd[1],
> ec_cmd[2],
> > - ec_cmd[3], ec_cmd[4], ec_cmd[5],
> ec_dbgfs_resp_bytes);
> > + pr_debug("olpc-ec: debugfs cmd 0x%02x with %d args %5ph,
> want %d returns\n",
> > + ec_cmd[0], ec_cmd_bytes, ec_cmd + 1,
> > + ec_dbgfs_resp_bytes);
> >
> > olpc_ec_cmd(ec_cmd[0], (ec_cmd_bytes == 0) ? NULL :
> &ec_cmd[1],
> > ec_cmd_bytes, ec_dbgfs_resp,
> ec_dbgfs_resp_bytes);
> >
> > - pr_debug("olpc-ec: response %02x %02x %02x %02x %02x %02x
> %02x %02x (%d bytes expected)\n",
> > - ec_dbgfs_resp[0], ec_dbgfs_resp[1],
> ec_dbgfs_resp[2],
> > - ec_dbgfs_resp[3], ec_dbgfs_resp[4],
> ec_dbgfs_resp[5],
> > - ec_dbgfs_resp[6], ec_dbgfs_resp[7],
> > - ec_dbgfs_resp_bytes);
> > + pr_debug("olpc-ec: response %8ph (%d bytes expected)\n",
> > + ec_dbgfs_resp, ec_dbgfs_resp_bytes);
> >
> > out:
> > mutex_unlock(&ec_dbgfs_lock);
> > --
> > 2.1.3
>
> =---------------------
> paul fox, pgf@laptop.org
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2015-09-30 15:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-29 12:26 [PATCH v1] OLPC: use %*ph specifier instead of passing direct values Andy Shevchenko
2014-12-29 14:32 ` Paul Fox
2015-09-30 14:59 ` Andy Shevchenko [this message]
2015-10-06 22:18 ` Darren Hart
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=1443625184.8361.310.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=dilinger@queued.net \
--cc=dvhart@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pgf@laptop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.