From: Stephen Hemminger <stephen@networkplumber.org>
To: Patrick Mahan <mahan@mahan.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Need to support mapping in bar1
Date: Fri, 9 Aug 2013 14:06:18 -0700 [thread overview]
Message-ID: <20130809140618.303aabbe@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <52054701.2050602@mahan.org>
On Fri, 09 Aug 2013 12:46:09 -0700
Patrick Mahan <mahan@mahan.org> wrote:
> Stephen,
>
> When did you generate this diff? It failed to apply to 1.3.1r2 so I am hand
> patching instead. But you might want to update to the latest version.
>
> Thanks,
>
> Patrick
>
Diff was against current git HEAD
next prev parent reply other threads:[~2013-08-09 21:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-08 23:45 Patrick Mahan
2013-08-08 23:53 ` Stephen Hemminger
2013-08-09 0:04 ` Patrick Mahan
2013-08-09 0:50 ` Stephen Hemminger
2013-08-09 19:46 ` Patrick Mahan
2013-08-09 21:06 ` Stephen Hemminger [this message]
2013-08-09 22:17 ` Stephen Hemminger
2013-08-13 21:50 ` Thomas Monjalon
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=20130809140618.303aabbe@nehalam.linuxnetplumber.net \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=mahan@mahan.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).