From: Kevin Traynor <ktraynor@redhat.com>
To: Igor Russkikh <Igor.Russkikh@aquantia.com>,
"dev@dpdk.org" <dev@dpdk.org>,
Pavel Belous <Pavel.Belous@aquantia.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 00/11] Aquantia atlantic bugfixes
Date: Wed, 8 May 2019 17:05:37 +0100 [thread overview]
Message-ID: <a1c72ce2-3def-f90f-cf79-6c84b713feb3@redhat.com> (raw)
Message-ID: <20190508160537.XYKGB7sr16GIhktQW_9rHKp_Ev15QxcKMUU_WUQh-NU@z> (raw)
In-Reply-To: <cover.1556525874.git.igor.russkikh@aquantia.com>
On 29/04/2019 09:20, 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.
>
> Igor Russkikh (7):
> net/atlantic: enable broadcast traffic
> net/atlantic: extra line at eof
> net/atlantic: bad indentation
> net/atlantic: fix max eeprom size
> net/atlantic: validity check for eeprom dev address
> net/atlantic: typo on args check
> net/atlantic: extra err check
>
> Pavel Belous (4):
> 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 | 43 +++++--
> drivers/net/atlantic/atl_rxtx.c | 1 -
> drivers/net/atlantic/atl_types.h | 3 +-
> 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 | 17 +--
> drivers/net/atlantic/hw_atl/hw_atl_utils.h | 11 +-
> .../net/atlantic/hw_atl/hw_atl_utils_fw2x.c | 111 ++++++++++++------
> 8 files changed, 128 insertions(+), 68 deletions(-)
>
Hi - some of these that are fixes will apply on 18.11 stable branch with
a little of rebasing, some will not. It will be cleaner to take the
fixes as a series. Can you send backports for the series for the 18.11
branch, or let me know if they are not needed.
thanks,
Kevin.
next prev parent reply other threads:[~2019-05-08 16:05 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-29 8:20 Igor Russkikh
2019-04-29 8:20 ` Igor Russkikh
2019-04-29 8:20 ` [dpdk-dev] [PATCH 01/11] net/atlantic: enable broadcast traffic Igor Russkikh
2019-04-29 8:20 ` Igor Russkikh
2019-04-29 8:20 ` [dpdk-dev] [PATCH 02/11] net/atlantic: extra line at eof Igor Russkikh
2019-04-29 8:20 ` Igor Russkikh
2019-04-29 13:57 ` Ferruh Yigit
2019-04-29 13:57 ` Ferruh Yigit
2019-04-29 8:20 ` [dpdk-dev] [PATCH 03/11] net/atlantic: bad indentation Igor Russkikh
2019-04-29 8:20 ` Igor Russkikh
2019-04-29 8:20 ` [dpdk-dev] [PATCH 04/11] net/atlantic: eeprom get/set should consider offset Igor Russkikh
2019-04-29 8:20 ` Igor Russkikh
2019-04-29 8:20 ` [dpdk-dev] [PATCH 05/11] net/atlantic: fix max eeprom size Igor Russkikh
2019-04-29 8:20 ` Igor Russkikh
2019-04-29 8:20 ` [dpdk-dev] [PATCH 06/11] net/atlantic: validity check for eeprom dev address Igor Russkikh
2019-04-29 8:20 ` Igor Russkikh
2019-04-29 8:20 ` [dpdk-dev] [PATCH 07/11] net/atlantic: bad logic with offsets talking with firmware Igor Russkikh
2019-04-29 8:20 ` Igor Russkikh
2019-04-29 8:20 ` [dpdk-dev] [PATCH 08/11] net/atlantic: flow control settings synchronization on rx Igor Russkikh
2019-04-29 8:20 ` Igor Russkikh
2019-04-29 8:20 ` [dpdk-dev] [PATCH 09/11] net/atlantic: use capability bits to detect eeprom access Igor Russkikh
2019-04-29 8:20 ` Igor Russkikh
2019-04-29 8:20 ` [dpdk-dev] [PATCH 10/11] net/atlantic: typo on args check Igor Russkikh
2019-04-29 8:20 ` Igor Russkikh
2019-04-29 8:20 ` [dpdk-dev] [PATCH 11/11] net/atlantic: extra err check Igor Russkikh
2019-04-29 8:20 ` Igor Russkikh
2019-05-08 16:05 ` Kevin Traynor [this message]
2019-05-08 16:05 ` [dpdk-dev] [PATCH 00/11] Aquantia atlantic bugfixes Kevin Traynor
2019-05-13 7:59 ` Igor Russkikh
2019-05-13 7:59 ` 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=a1c72ce2-3def-f90f-cf79-6c84b713feb3@redhat.com \
--to=ktraynor@redhat.com \
--cc=Igor.Russkikh@aquantia.com \
--cc=Pavel.Belous@aquantia.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).