DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Andrew Rybchenko <arybchenko@solarflare.com>,
	Stephen Hemminger <stephen@networkplumber.org>,
	dev@dpdk.org
Cc: Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] doc: add deprecation notice about changes to ethernet structures
Date: Wed, 31 Jul 2019 11:46:00 +0100	[thread overview]
Message-ID: <200e4702-5c00-f62c-6538-ae64f76c1014@intel.com> (raw)
In-Reply-To: <6f248d5e-22b1-da4a-00f1-972bf51a3a30@solarflare.com>

On 7/23/2019 12:28 PM, Andrew Rybchenko wrote:
> On 7/19/19 7:56 PM, Stephen Hemminger wrote:
>> Tell users about upcoming changes to rte_ether_addr and
>> rte_ether_header.
>>
>> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
>> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
> 
> Acked-by: Andrew Rybchenko <arybchenko@solarflare.com>
> 

Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>

  reply	other threads:[~2019-07-31 10:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-09 14:58 [dpdk-dev] [PATCH] doc: deprecation notice for change of ether struct alignment Bruce Richardson
2019-07-09 14:59 ` Stephen Hemminger
2019-07-09 15:02   ` Bruce Richardson
2019-07-18 22:09     ` [dpdk-dev] [PATCH] doc: add deprecation notice about changes to ethernet structures Stephen Hemminger
2019-07-19 10:57       ` Bruce Richardson
2019-07-19 16:56     ` [dpdk-dev] [PATCH v2] " Stephen Hemminger
2019-07-23 11:28       ` Andrew Rybchenko
2019-07-31 10:46         ` Ferruh Yigit [this message]
2019-08-06 11:26           ` Thomas Monjalon
2019-08-10 20:22             ` 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=200e4702-5c00-f62c-6538-ae64f76c1014@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=arybchenko@solarflare.com \
    --cc=bruce.richardson@intel.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).