From: Igor Russkikh <Igor.Russkikh@aquantia.com>
To: Kevin Traynor <ktraynor@redhat.com>,
"dev@dpdk.org" <dev@dpdk.org>,
Pavel Belous <Pavel.Belous@aquantia.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH 00/11] Aquantia atlantic bugfixes
Date: Mon, 13 May 2019 07:59:54 +0000 [thread overview]
Message-ID: <bde67b78-c723-91db-b627-ba3ea2f7c380@aquantia.com> (raw)
In-Reply-To: <a1c72ce2-3def-f90f-cf79-6c84b713feb3@redhat.com>
>
> 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.
Hi Kevin, I'll backport these to 18.11 and resubmit it soon.
Thanks,
Igor
prev parent reply other threads:[~2019-05-13 8:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1556525874.git.igor.russkikh@aquantia.com>
2019-04-29 8:20 ` [dpdk-stable] [PATCH 01/11] net/atlantic: enable broadcast traffic Igor Russkikh
2019-04-29 8:20 ` [dpdk-stable] [PATCH 04/11] net/atlantic: eeprom get/set should consider offset Igor Russkikh
2019-04-29 8:20 ` [dpdk-stable] [PATCH 05/11] net/atlantic: fix max eeprom size Igor Russkikh
2019-04-29 8:20 ` [dpdk-stable] [PATCH 07/11] net/atlantic: bad logic with offsets talking with firmware Igor Russkikh
2019-04-29 8:20 ` [dpdk-stable] [PATCH 08/11] net/atlantic: flow control settings synchronization on rx Igor Russkikh
2019-05-08 16:05 ` [dpdk-stable] [dpdk-dev] [PATCH 00/11] Aquantia atlantic bugfixes Kevin Traynor
2019-05-13 7:59 ` Igor Russkikh [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=bde67b78-c723-91db-b627-ba3ea2f7c380@aquantia.com \
--to=igor.russkikh@aquantia.com \
--cc=Pavel.Belous@aquantia.com \
--cc=dev@dpdk.org \
--cc=ktraynor@redhat.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).