From: "Wu, Jingjing" <jingjing.wu@intel.com>
To: "Jastrzebski, MichalX K" <michalx.k.jastrzebski@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "Jain, Deepak K" <deepak.k.jain@intel.com>,
"Doherty, Declan" <declan.doherty@intel.com>,
"Jastrzebski, MichalX K" <michalx.k.jastrzebski@intel.com>
Subject: Re: [dpdk-dev] [PATCH] app/testpmd: fix bonding initialization due to unproper name
Date: Fri, 21 Jul 2017 02:29:11 +0000 [thread overview]
Message-ID: <9BB6961774997848B5B42BEC655768F810DCD41E@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <20170713094832.16904-1-michalx.k.jastrzebski@intel.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Michal Jastrzebski
> Sent: Thursday, July 13, 2017 5:49 PM
> To: dev@dpdk.org
> Cc: Jain, Deepak K <deepak.k.jain@intel.com>; Doherty, Declan
> <declan.doherty@intel.com>; Jastrzebski, MichalX K
> <michalx.k.jastrzebski@intel.com>
> Subject: [dpdk-dev] [PATCH] app/testpmd: fix bonding initialization due to
> unproper name
>
> when creating a bond device in testpmd, a name for a device must meet the
> correct convention described in the documentation:
> The device name must start with the net_bonding prefix followed by numbers
> or letters.
> Change for ALB mempool allocation - mem_name was too long.
>
> Fixes: 9bf4901d1a11 ("bus/vdev: remove probe with driver name option")
>
> Signed-off-by: Michal Jastrzebski <michalx.k.jastrzebski@intel.com>
Reviewed-by: Jingjing Wu <jingjing.wu@intel.com>
next prev parent reply other threads:[~2017-07-21 2:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-13 9:48 Michal Jastrzebski
2017-07-21 2:29 ` Wu, Jingjing [this message]
2017-07-21 6:37 ` 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=9BB6961774997848B5B42BEC655768F810DCD41E@SHSMSX103.ccr.corp.intel.com \
--to=jingjing.wu@intel.com \
--cc=declan.doherty@intel.com \
--cc=deepak.k.jain@intel.com \
--cc=dev@dpdk.org \
--cc=michalx.k.jastrzebski@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).