From: Matthew Hall <mhall@mhcomputing.net>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] rc1 / call for review
Date: Mon, 29 Sep 2014 14:33:41 -0700 [thread overview]
Message-ID: <20140929213341.GA589@mhcomputing.net> (raw)
In-Reply-To: <1963310.3iizrFVzmj@xps13>
On Mon, Sep 29, 2014 at 10:23:58PM +0200, Thomas Monjalon wrote:
> - mbuf rework
> - logs rework
> - some eal cleanups
Hi Thomas,
I was curious, did we happen to know if any of these three changes affected
the external API's much?
It would help us get some idea what to test and where to look, since mbuf,
logs, and eal are probably the three most popular parts of DPDK for us app
hackers to interact with regularly.
Thanks,
Matthew.
next prev parent reply other threads:[~2014-09-29 21:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-29 20:23 Thomas Monjalon
2014-09-29 21:33 ` Matthew Hall [this message]
2014-09-30 4:52 ` Thomas Monjalon
2014-09-30 5:29 ` Matthew Hall
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=20140929213341.GA589@mhcomputing.net \
--to=mhall@mhcomputing.net \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.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).