From: Kevin Traynor <ktraynor@redhat.com>
To: Igor Russkikh <Igor.Russkikh@aquantia.com>,
"stable@dpdk.org" <stable@dpdk.org>
Cc: Pavel Belous <Pavel.Belous@aquantia.com>
Subject: Re: [dpdk-stable] [PATCH 18.11 00/10] Aquantia atlantic bugfixes
Date: Mon, 20 May 2019 17:20:28 +0100 [thread overview]
Message-ID: <ebedd196-fcc7-3d2e-fc78-9f0ffb57e37b@redhat.com> (raw)
In-Reply-To: <cover.1558172288.git.igor.russkikh@aquantia.com>
On 18/05/2019 10:47, Igor Russkikh wrote:
> This patchset contains various bugfixes found during verification
> and integration testing.
>
> Most notable is eeprom access cleanup, fix for broadcast filter,
> flow control logic tracking, some code style cleanups.
>
> Backported patchset
>
> https://patches.dpdk.org/cover/53130/
>
> to 18.11 stable
>
Hi Igor, some of these patches won't apply, can you rebase against the
latest on dpdk-stable 18.11 branch.
Kevin.
> Igor Russkikh (5):
> net/atlantic: enable broadcast traffic
> net/atlantic: extra line at eof
> net/atlantic: fix max eeprom size
> net/atlantic: validity check for eeprom dev address
> net/atlantic: fix link configuration
>
> Pavel Belous (5):
> net/atlantic: error handling for mailbox access
> net/atlantic: eeprom get/set should consider offset
> net/atlantic: bad logic with offsets talking with firmware
> net/atlantic: flow control settings synchronization on rx
> net/atlantic: use capability bits to detect eeprom access
>
> drivers/net/atlantic/atl_ethdev.c | 102 +++++++++-----
> drivers/net/atlantic/atl_rxtx.c | 1 -
> drivers/net/atlantic/atl_types.h | 9 +-
> drivers/net/atlantic/hw_atl/hw_atl_b0.c | 8 ++
> drivers/net/atlantic/hw_atl/hw_atl_b0.h | 2 +
> drivers/net/atlantic/hw_atl/hw_atl_utils.c | 14 +-
> drivers/net/atlantic/hw_atl/hw_atl_utils.h | 16 +--
> .../net/atlantic/hw_atl/hw_atl_utils_fw2x.c | 130 +++++++++++++-----
> 8 files changed, 193 insertions(+), 89 deletions(-)
>
next prev parent reply other threads:[~2019-05-20 16:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-18 9:47 Igor Russkikh
2019-05-18 9:47 ` [dpdk-stable] [PATCH 18.11 01/10] net/atlantic: enable broadcast traffic Igor Russkikh
2019-05-18 9:47 ` [dpdk-stable] [PATCH 18.11 02/10] net/atlantic: extra line at eof Igor Russkikh
2019-05-18 9:47 ` [dpdk-stable] [PATCH 18.11 03/10] net/atlantic: error handling for mailbox access Igor Russkikh
2019-05-18 9:47 ` [dpdk-stable] [PATCH 18.11 04/10] net/atlantic: eeprom get/set should consider offset Igor Russkikh
2019-05-18 9:47 ` [dpdk-stable] [PATCH 18.11 05/10] net/atlantic: fix max eeprom size Igor Russkikh
2019-05-18 9:47 ` [dpdk-stable] [PATCH 18.11 06/10] net/atlantic: validity check for eeprom dev address Igor Russkikh
2019-05-18 9:47 ` [dpdk-stable] [PATCH 18.11 07/10] net/atlantic: bad logic with offsets talking with firmware Igor Russkikh
2019-05-18 9:47 ` [dpdk-stable] [PATCH 18.11 08/10] net/atlantic: flow control settings synchronization on rx Igor Russkikh
2019-05-18 9:47 ` [dpdk-stable] [PATCH 18.11 09/10] net/atlantic: use capability bits to detect eeprom access Igor Russkikh
2019-05-18 9:47 ` [dpdk-stable] [PATCH 18.11 10/10] net/atlantic: fix link configuration Igor Russkikh
2019-05-20 16:20 ` Kevin Traynor [this message]
2019-05-21 8:57 ` [dpdk-stable] [PATCH 18.11 00/10] Aquantia atlantic bugfixes Igor Russkikh
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=ebedd196-fcc7-3d2e-fc78-9f0ffb57e37b@redhat.com \
--to=ktraynor@redhat.com \
--cc=Igor.Russkikh@aquantia.com \
--cc=Pavel.Belous@aquantia.com \
--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).