DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 0/2] net/netvsc: fix secondary process issues
Date: Tue, 14 Jan 2020 16:51:43 +0000	[thread overview]
Message-ID: <b3450a32-8cf8-882c-ea7b-025b9dda2237@intel.com> (raw)
In-Reply-To: <20200113191239.22750-1-stephen@networkplumber.org>

On 1/13/2020 7:12 PM, Stephen Hemminger wrote:
> First patch is a bug fix for crash in info_get in secondary process.
> Second one is modification to prevent similar issues in future.
> 
> Stephen Hemminger (2):
>   net/netvsc: fix crash in secondary process
>   net/netvsc: eliminate numa specific allocation for control messages
> 

Series applied to dpdk-next-net/master, thanks.

      parent reply	other threads:[~2020-01-14 16:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-13 19:12 Stephen Hemminger
2020-01-13 19:12 ` [dpdk-dev] [PATCH 1/2] net/netvsc: fix crash in secondary process Stephen Hemminger
2020-01-13 19:12 ` [dpdk-dev] [PATCH 2/2] net/netvsc: eliminate numa specific allocation for control messages Stephen Hemminger
2020-01-14 16:51 ` 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=b3450a32-8cf8-882c-ea7b-025b9dda2237@intel.com \
    --to=ferruh.yigit@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).