From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Andrew Boyer <aboyer@pensando.io>, dev@dpdk.org
Cc: Alfredo Cardigliano <cardigliano@ntop.org>
Subject: Re: [dpdk-dev] [PATCH 0/6] net/ionic: fix device configuration and init
Date: Mon, 18 Jan 2021 17:09:53 +0000 [thread overview]
Message-ID: <97c3905c-7114-2fef-3abe-1518de962b64@intel.com> (raw)
In-Reply-To: <20210111190209.70928-1-aboyer@pensando.io>
On 1/11/2021 7:02 PM, Andrew Boyer wrote:
> This patch series fixes up configuration flag handling, fixes up
> link autonegotiation, and reduces the init time.
>
> DTS was used to identify the issues and verify the fixes.
>
> Andrew Boyer (6):
> net/ionic: revise configuration flag handling
> net/ionic: combine queue init and enable commands
> net/ionic: set port admin state to up in port init
> net/ionic: don't add station MAC filter on init
> net/ionic: clear up confusion around FC autoneg
> net/ionic: correctly set link speed and autonegotiation
>
Series applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2021-01-18 17:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-11 19:02 Andrew Boyer
2021-01-11 19:02 ` [dpdk-dev] [PATCH 1/6] net/ionic: revise configuration flag handling Andrew Boyer
2021-01-11 19:02 ` [dpdk-dev] [PATCH 2/6] net/ionic: combine queue init and enable commands Andrew Boyer
2021-01-11 19:02 ` [dpdk-dev] [PATCH 3/6] net/ionic: set port admin state to up in port init Andrew Boyer
2021-01-11 19:02 ` [dpdk-dev] [PATCH 4/6] net/ionic: don't add station MAC filter on init Andrew Boyer
2021-01-11 19:02 ` [dpdk-dev] [PATCH 5/6] net/ionic: clear up confusion around FC autoneg Andrew Boyer
2021-01-11 19:02 ` [dpdk-dev] [PATCH 6/6] net/ionic: correctly set link speed and autonegotiation Andrew Boyer
2021-01-18 17:10 ` Ferruh Yigit
2021-01-18 17:09 ` Ferruh Yigit [this message]
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=97c3905c-7114-2fef-3abe-1518de962b64@intel.com \
--to=ferruh.yigit@intel.com \
--cc=aboyer@pensando.io \
--cc=cardigliano@ntop.org \
--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).