From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: netdev@vger.kernel.org,
Peter P Waskiewicz Jr <peter.p.waskiewicz.jr@intel.com>,
e1000-devel@lists.sourceforge.net
Subject: Re: [E1000-devel] [PATCH] e100: dump small buffers via %*phC
Date: Wed, 31 Jul 2013 05:32:57 -0700 [thread overview]
Message-ID: <1375273977.2877.42.camel@jtkirshe-mobl> (raw)
In-Reply-To: <1375273205.31118.68.camel@smile>
[-- Attachment #1: Type: text/plain, Size: 920 bytes --]
On Wed, 2013-07-31 at 15:20 +0300, Andy Shevchenko wrote:
> On Fri, 2013-07-26 at 04:12 -0700, Jeff Kirsher wrote:
> > On Thu, 2013-07-25 at 14:24 +0300, Andy Shevchenko wrote:
> > > There is nice specifier in kernel that allows us to print small
> > > buffers easily.
> > >
> > > Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> > > ---
> > > drivers/net/ethernet/intel/e100.c | 15 ++++++---------
> > > 1 file changed, 6 insertions(+), 9 deletions(-)
> >
> > Thanks, I appreciate you sending this again...
> >
> > I already have this patch queued up for upstream and it will be in
> the
> > next series I send.
>
> Oh, sorry for resending.
> I cleared up my queue after rebasing to recent linux-next, where the
> patch is not appeared yet, that's why duplicate was created.
No problem, sorry for the delay in getting it upstream and feel free to
ping me next time.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2013-07-31 12:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-25 11:24 [PATCH] e100: dump small buffers via %*phC Andy Shevchenko
2013-07-26 11:12 ` [E1000-devel] " Jeff Kirsher
2013-07-31 12:20 ` Andy Shevchenko
2013-07-31 12:32 ` Jeff Kirsher [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=1375273977.2877.42.camel@jtkirshe-mobl \
--to=jeffrey.t.kirsher@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=netdev@vger.kernel.org \
--cc=peter.p.waskiewicz.jr@intel.com \
/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).