From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Andrew Rybchenko <arybchenko@solarflare.com>, dev@dpdk.org
Cc: stable@dpdk.org
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH] net/sfc: fix speed capabilities reported in device info
Date: Thu, 21 Mar 2019 18:06:59 +0000 [thread overview]
Message-ID: <90df6695-6551-3fe2-fdb9-9d06244e64ad@intel.com> (raw)
Message-ID: <20190321180659.3s6bPuipHTepXRSstnZSXFaqLnqrSqNBYiPRVw8d6PU@z> (raw)
In-Reply-To: <1553013360-12880-1-git-send-email-arybchenko@solarflare.com>
On 3/19/2019 4:36 PM, Andrew Rybchenko wrote:
> Phy capabilities are bit offsets in libefx, but was used as bit masks.
>
> Fixes: d23f3a89ab54 ("net/sfc: support link speed and duplex settings")
> Fixes: f82e33afbbb9 ("net/sfc: support link speeds up to 100G")
> Cc: stable@dpdk.org
>
> Signed-off-by: Andrew Rybchenko <arybchenko@solarflare.com>
Applied to dpdk-next-net/master, thanks.
next prev parent reply other threads:[~2019-03-21 18:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-19 16:36 [dpdk-dev] " Andrew Rybchenko
2019-03-19 16:36 ` Andrew Rybchenko
2019-03-21 18:06 ` Ferruh Yigit [this message]
2019-03-21 18:06 ` [dpdk-dev] [dpdk-stable] " 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=90df6695-6551-3fe2-fdb9-9d06244e64ad@intel.com \
--to=ferruh.yigit@intel.com \
--cc=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--cc=stable@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).