From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Andrew Rybchenko <arybchenko@solarflare.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 0/4] Solarflare PMD link status and flow control fixes
Date: Mon, 16 Jan 2017 17:07:10 +0000 [thread overview]
Message-ID: <f3a73069-978b-b767-4934-31762967f029@intel.com> (raw)
In-Reply-To: <1484211803-21449-1-git-send-email-arybchenko@solarflare.com>
On 1/12/2017 9:03 AM, Andrew Rybchenko wrote:
> Fix few problems with link status information and flow control settings.
>
> Patches are grouped into a series since flow control fix discovers
> link status sync issue just after port start.
>
> Andrew Rybchenko (4):
> net/sfc: avoid usage of possibly uninitialized link_mode
> net/sfc: sync link status knowledge with HW on start
> net/sfc: report correct link status when port is not started
> net/sfc: fix flow control settings set on port start
<...>
Hi Andrew,
These are fixes to the code in next-net, and used fixes tags with commit
ids from next-net. But next-net is allowed to re-write the git history,
so those commit ids may change.
That is why I am waiting the RC1, when next-net merged into main tree,
commit ids will be fixed after that point and can get these fixes.
Regards,
ferruh
next prev parent reply other threads:[~2017-01-16 17:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-12 9:03 Andrew Rybchenko
2017-01-12 9:03 ` [dpdk-dev] [PATCH 1/4] net/sfc: avoid usage of possibly uninitialized link_mode Andrew Rybchenko
2017-01-12 9:03 ` [dpdk-dev] [PATCH 2/4] net/sfc: sync link status knowledge with HW on start Andrew Rybchenko
2017-01-12 9:03 ` [dpdk-dev] [PATCH 3/4] net/sfc: report correct link status when port is not started Andrew Rybchenko
2017-01-12 9:03 ` [dpdk-dev] [PATCH 4/4] net/sfc: fix flow control settings set on port start Andrew Rybchenko
2017-01-16 17:07 ` Ferruh Yigit [this message]
2017-01-18 19:23 ` [dpdk-dev] [PATCH 0/4] Solarflare PMD link status and flow control fixes 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=f3a73069-978b-b767-4934-31762967f029@intel.com \
--to=ferruh.yigit@intel.com \
--cc=arybchenko@solarflare.com \
--cc=dev@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).