From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
Stephen Hemminger <stephen@networkplumber.org>, <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net: make rte_ether_unformat_addr stable
Date: Wed, 1 Sep 2021 09:49:09 +0100 [thread overview]
Message-ID: <baf14c37-6e13-0327-d27e-6940f0555525@intel.com> (raw)
In-Reply-To: <cfb983d9-9fae-1d80-11e0-cd9fd78c7990@oktetlabs.ru>
On 9/1/2021 8:11 AM, Andrew Rybchenko wrote:
> On 8/31/21 11:07 PM, Stephen Hemminger wrote:
>> This function has been in since 19.11.
>>
>> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
>
> Acked-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
>
Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
next prev parent reply other threads:[~2021-09-01 8:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-31 20:07 Stephen Hemminger
2021-09-01 7:11 ` Andrew Rybchenko
2021-09-01 8:49 ` Ferruh Yigit [this message]
2021-09-16 11:35 ` Olivier Matz
2021-10-02 9:38 ` David Marchand
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=baf14c37-6e13-0327-d27e-6940f0555525@intel.com \
--to=ferruh.yigit@intel.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--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).