From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Bernard Iremonger <bernard.iremonger@intel.com>,
dev@dpdk.org, jingjing.wu@intel.com
Cc: stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH v6 1/3] net/i40e: fix segmentation fault in close
Date: Fri, 27 Jan 2017 13:21:16 +0000 [thread overview]
Message-ID: <a6459092-3491-9381-7fcc-8cbe238e3c6e@intel.com> (raw)
In-Reply-To: <1485512567-16668-1-git-send-email-bernard.iremonger@intel.com>
On 1/27/2017 10:22 AM, Bernard Iremonger wrote:
> Change the order of releasing the vsi's.
> Release the vmdq vsi's first, then release the main vsi.
>
> Fixes: 4861cde46116 ("i40e: new poll mode driver")
>
> CC: stable@dpdk.org
>
> Signed-off-by: Bernard Iremonger <bernard.iremonger@intel.com>
> Acked-by: Jingjing Wu <jingjing.wu@intel.com>
Fixes: 3cb446b4aeb2 ("i40e: free vmdq vsi when closing")
Cc: stable@dpdk.org
Applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2017-01-27 13:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-27 10:22 Bernard Iremonger
2017-01-27 13:21 ` Ferruh Yigit [this message]
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=a6459092-3491-9381-7fcc-8cbe238e3c6e@intel.com \
--to=ferruh.yigit@intel.com \
--cc=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
--cc=stable@dpdk.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).