From: Olivier Matz <olivier.matz@6wind.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: "Lu, Wenzhuo" <wenzhuo.lu@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [RFC] lib/librte_ether: add a return value for MAC set ops
Date: Mon, 29 Jan 2018 09:25:07 +0100 [thread overview]
Message-ID: <20180129082507.qlbqbnamhfye5ghk@platinum> (raw)
In-Reply-To: <460287e3-db94-b677-e262-4c45a59fb486@intel.com>
Hi,
On Fri, Jan 26, 2018 at 04:54:43PM +0000, Ferruh Yigit wrote:
> On 1/26/2018 2:19 AM, Lu, Wenzhuo wrote:
> > Hi Olivier,
> >
> >
> >> -----Original Message-----
> >> From: Olivier Matz [mailto:olivier.matz@6wind.com]
> >> Sent: Thursday, January 25, 2018 6:40 PM
> >> To: Lu, Wenzhuo <wenzhuo.lu@intel.com>
> >> Cc: dev@dpdk.org
> >> Subject: Re: [dpdk-dev] [RFC] lib/librte_ether: add a return value for MAC set
> >> ops
> >>
> >> Hi Wenzhuo,
> >>
> >> On Thu, Jan 25, 2018 at 10:46:57AM +0800, Wenzhuo Lu wrote:
> >>> Setting the default MAC address may fail on many NICs.
> >>> But the ops return void. So, even it failed, RTE changes the MAC
> >>> address and APP doesn't know the failure.
> >>>
> >>> It's not real patch, just show the idea to add a return value for the
> >>> ops.
> >>
> >> Thank you for taking care of this. I had some plans to work on it too, as
> >> discussed here:
> >> https://dpdk.org/dev/patchwork/patch/32284/
> > Sorry, didn't notice that. Glad to know you're working on that. So you'll continue, right?
>
> Plan was send PMD fixes and deprecation notice on this release and send fix next
> release [1].
>
> I think PMD fixes are merged now, but deprecation notice not send yet.
>
> [1]
> https://dpdk.org/ml/archives/dev/2018-January/085195.html
Yes, I'll send the deprecation notice today.
next prev parent reply other threads:[~2018-01-29 8:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-25 2:46 Wenzhuo Lu
2018-01-25 10:40 ` Olivier Matz
2018-01-26 2:19 ` Lu, Wenzhuo
2018-01-26 16:54 ` Ferruh Yigit
2018-01-29 8:25 ` Olivier Matz [this message]
2018-05-22 22:47 ` 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=20180129082507.qlbqbnamhfye5ghk@platinum \
--to=olivier.matz@6wind.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=wenzhuo.lu@intel.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).