From: Ferruh Yigit <ferruh.yigit@intel.com>
To: yaochuhong <ych@panath.cn>, shijith.thotton@cavium.com
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 3/3] add signoff
Date: Mon, 21 May 2018 11:07:05 +0100 [thread overview]
Message-ID: <3ebb588f-5d51-db37-e396-e611366487a8@intel.com> (raw)
In-Reply-To: <1526865655-59863-3-git-send-email-ych@panath.cn>
On 5/21/2018 2:20 AM, yaochuhong wrote:
> Signed-off-by: yaochuhong <ych@panath.cn>
Hi Yao,
Thanks for contribution.
Can you please send this as a single patch, and for sign off please follow
Signed-off-by: Name Surname <e-mail@all_lower.case>
There is some documentation about how to prepare and send a patch that may help:
https://dpdk.org/doc/guides/contributing/patches.html
> ---
> drivers/net/liquidio/lio_ethdev.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/net/liquidio/lio_ethdev.c b/drivers/net/liquidio/lio_ethdev.c
> index 0a6eb55..a6a37c8 100644
> --- a/drivers/net/liquidio/lio_ethdev.c
> +++ b/drivers/net/liquidio/lio_ethdev.c
> @@ -1405,7 +1405,7 @@ struct rte_lio_xstats_name_off {
> /* Configure RSS if device configured with multiple RX queues. */
> lio_dev_mq_rx_configure(eth_dev);
>
> - /* Before update the link info, must set link_status64 to 0. */
> + /* Before update the link info, must set linfo.link.link_status64 to 0. */
> lio_dev->linfo.link.link_status64 = 0;
>
> /* start polling for lsc */
>
next prev parent reply other threads:[~2018-05-21 10:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-21 1:20 [dpdk-dev] [PATCH 1/3] net liquidio fix Unable to update lio_dev->linfo.link var yaochuhong
2018-05-21 1:20 ` [dpdk-dev] [PATCH 2/3] fix Coding Style yaochuhong
2018-05-21 1:20 ` [dpdk-dev] [PATCH 3/3] add signoff yaochuhong
2018-05-21 10:07 ` Ferruh Yigit [this message]
2018-05-21 10:11 ` Yao chuhong
2018-05-21 6:55 ` [dpdk-dev] [PATCH 1/3] net liquidio fix Unable to update lio_dev->linfo.link var Stephen Hemminger
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=3ebb588f-5d51-db37-e396-e611366487a8@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=shijith.thotton@cavium.com \
--cc=ych@panath.cn \
/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).