All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Wangxiaoyun (Cloud)" <cloud.wangxiaoyun@huawei.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>, <dev@dpdk.org>
Cc: <bluca@debian.org>, <luoxianjun@huawei.com>,
	<luoxingyu@huawei.com>, <zhouguoyang@huawei.com>,
	<xuanziyang2@huawei.com>, <shahar.belkar@huawei.com>,
	<yin.yinshi@huawei.com>
Subject: Re: [dpdk-dev] [PATCH v3 1/2] net/hinic/base: fix FW hotactive problem
Date: Fri, 10 Apr 2020 16:40:08 +0800	[thread overview]
Message-ID: <fed0a0d9-db76-e5fe-2c59-03354c598b0c@huawei.com> (raw)
In-Reply-To: <8eb0f013-7a65-bb13-9ae5-004bc7ff71bc@intel.com>

Hi Ferruch，
     I will upstream a new patch to clarify the comments.
Best regards
xiaoyun wang

在 2020/4/4 1:24, Ferruh Yigit 写道:
> On 4/1/2020 10:30 AM, Xiaoyun wang wrote:
>> When PF detects FW is hotactive, up returns HINIC_DEV_BUSY_ACTIVE_FW for
> 
> Hi Xiaoyun,
> 
> What is 'hotactive'? "hot active"? Does it mean FW busy?
> 
>> pf driver, when cmdq reinit at txrx flush, cmdq will fail, driver should
>> reinit the cmdq when port start.
> 
> Can you please rephrase above message to clarify it?
> 
>>
>> Fixes: d9ce1917941c ("net/hinic/base: add hardware operation")
>> Signed-off-by: Xiaoyun wang <cloud.wangxiaoyun@huawei.com>
> 
> <...>
> 
> 
> .
> 


  reply	other threads:[~2020-04-10  8:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-01  9:29 [dpdk-dev] [PATCH v3 0/2] bug fixes Xiaoyun wang
2020-04-01  9:30 ` [dpdk-dev] [PATCH v3 1/2] net/hinic/base: fix FW hotactive problem Xiaoyun wang
2020-04-01  9:28   ` Kevin Traynor
2020-04-03 17:24   ` Ferruh Yigit
2020-04-10  8:40     ` Wangxiaoyun (Cloud) [this message]
2020-04-01  9:30 ` [dpdk-dev] [PATCH v3 2/2] net/hinic/base: optimize log style Xiaoyun wang

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=fed0a0d9-db76-e5fe-2c59-03354c598b0c@huawei.com \
    --to=cloud.wangxiaoyun@huawei.com \
    --cc=bluca@debian.org \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=luoxianjun@huawei.com \
    --cc=luoxingyu@huawei.com \
    --cc=shahar.belkar@huawei.com \
    --cc=xuanziyang2@huawei.com \
    --cc=yin.yinshi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.