From: Jesse Brandeburg <jesse.brandeburg@intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
<intel-wired-lan@lists.osuosl.org>, <netdev@vger.kernel.org>,
jesse.brandeburg@intel.com
Subject: Re: [PATCH 1/1] i40e: re-use %*ph specifier to hexdump a data
Date: Fri, 9 Oct 2015 13:28:57 -0700 [thread overview]
Message-ID: <20151009132857.00002b95@unknown> (raw)
In-Reply-To: <1443777496-43299-1-git-send-email-andriy.shevchenko@linux.intel.com>
On Fri, 2 Oct 2015 12:18:16 +0300
Andy Shevchenko <andriy.shevchenko@linux.intel.com> wrote:
> Instead of using a custom approach change the code to use %*ph format
> specifier.
>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Nice catch, thanks!
Acked-by: jesse Brandeburg <jesse.brandeburg@intel.com>
prev parent reply other threads:[~2015-10-09 20:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-02 9:18 [PATCH 1/1] i40e: re-use %*ph specifier to hexdump a data Andy Shevchenko
2015-10-09 20:28 ` Jesse Brandeburg [this message]
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=20151009132857.00002b95@unknown \
--to=jesse.brandeburg@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=netdev@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).