patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Guoyang Zhou <zhouguoyang@huawei.com>, dev@dpdk.org
Cc: bluca@debian.org, cloud.wangxiaoyun@huawei.com,
	luoxianjun@huawei.com, yin.yinshi@huawei.com,
	luojiachen@huawei.com, chenlizhong@huawei.com,
	zengweiliang.zengweiliang@huawei.com, liqingqing3@huawei.com,
	stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH v2 1/1] net/hinic: fix coredump when in secondary process
Date: Fri, 26 Mar 2021 10:28:06 +0000	[thread overview]
Message-ID: <4f4d7203-01fb-679d-beb7-fae16d4fcaad@intel.com> (raw)
In-Reply-To: <b9908924e1a0a0487f067e21195af628b5efde24.1616504799.git.zhouguoyang@huawei.com>

On 3/23/2021 1:17 PM, Guoyang Zhou wrote:
> Some apps, such as fstack, will use secondary process to access the
> memory of eth_dev_ops, and they want to get the info of dev, but hinic
> driver does not initialized it when in secondary process.
> 
> Fixes: 66f64dd6dc86 ("net/hinic: fix secondary process")
> Cc: stable@dpdk.org
> Signed-off-by: Guoyang Zhou <zhouguoyang@huawei.com>

Some comments from previous versions seems outstanding, can you please 
check/comment on them please:

http://inbox.dpdk.org/dev/c3ceb0c3-4d35-c14e-ea6b-cd4b311657a4@intel.com/


Also can you please send a new version as reply to previous version?
This keeps different versions in same email thread and helps to find the 
comments/discussing to previous versions easier. You can do this  via "git 
send-email", '--in-reply-to' argument.

  reply	other threads:[~2021-03-26 10:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1616504799.git.zhouguoyang@huawei.com>
2021-03-23 13:17 ` Guoyang Zhou
2021-03-26 10:28   ` Ferruh Yigit [this message]
2021-03-30 13:06   ` Ferruh Yigit

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=4f4d7203-01fb-679d-beb7-fae16d4fcaad@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=bluca@debian.org \
    --cc=chenlizhong@huawei.com \
    --cc=cloud.wangxiaoyun@huawei.com \
    --cc=dev@dpdk.org \
    --cc=liqingqing3@huawei.com \
    --cc=luojiachen@huawei.com \
    --cc=luoxianjun@huawei.com \
    --cc=stable@dpdk.org \
    --cc=yin.yinshi@huawei.com \
    --cc=zengweiliang.zengweiliang@huawei.com \
    --cc=zhouguoyang@huawei.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).