From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] doc: announce API change for rte_ether.h
Date: Mon, 14 Dec 2015 15:54:06 +0100 [thread overview]
Message-ID: <2618453.kF8WIUB5uB@xps13> (raw)
In-Reply-To: <1449790022-24126-1-git-send-email-stephen@networkplumber.org>
2015-12-10 15:27, Stephen Hemminger:
> Plan to change to <net/ethernet.h> version of struct ether_addr in
> DPDK 2.3. The change in DPDK source is trivial but it will impact
> source compatablilty therefore notification is necessary.
[...]
> +* librte_ether: The structure ether_addr in DPDK will be replaced
> + by using the standard header file <net/ethernet.h>. The structure
> + size will be the same (no ABI impact), but the structure field name
> + will change from addr_bytes[] to ether_addr_octet[].
Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
Any other votes for this API cleanup?
next prev parent reply other threads:[~2015-12-14 14:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-10 23:27 Stephen Hemminger
2015-12-11 9:28 ` Panu Matilainen
2015-12-11 16:33 ` Stephen Hemminger
2015-12-14 14:54 ` Thomas Monjalon [this message]
2015-12-14 15:30 ` Bruce Richardson
2015-12-14 15:41 ` Thomas Monjalon
2015-12-14 16:00 ` Bruce Richardson
2015-12-14 17:30 ` Stephen Hemminger
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=2618453.kF8WIUB5uB@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.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).