From: Andrew Lunn <andrew@lunn.ch>
To: Igor Russkikh <Igor.Russkikh@aquantia.com>
Cc: "David S . Miller" <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next v2 3/8] maintainers: declare aquantia atlantic driver maintenance
Date: Tue, 25 Jun 2019 00:16:20 +0200 [thread overview]
Message-ID: <20190624221620.GF31306@lunn.ch> (raw)
In-Reply-To: <2b413d26ebc04cfca7f7dfa5422f1ea28d9cd76d.1561388549.git.igor.russkikh@aquantia.com>
On Mon, Jun 24, 2019 at 03:10:49PM +0000, Igor Russkikh wrote:
> Aquantia is resposible now for all new features and bugfixes.
> Reflect that in MAINTAINERS.
>
> Signed-off-by: Igor Russkikh <igor.russkikh@aquantia.com>
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Andrew
next prev parent reply other threads:[~2019-06-24 22:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-24 15:10 [PATCH net-next v2 0/8] net: aquantia: implement vlan offloads Igor Russkikh
2019-06-24 15:10 ` [PATCH net-next v2 1/8] net: aquantia: replace internal driver version code with uts Igor Russkikh
2019-06-24 22:08 ` Andrew Lunn
2019-06-24 15:10 ` [PATCH net-next v2 2/8] net: aquantia: add documentation for the atlantic driver Igor Russkikh
2019-06-24 22:15 ` Andrew Lunn
2019-06-24 15:10 ` [PATCH net-next v2 3/8] maintainers: declare aquantia atlantic driver maintenance Igor Russkikh
2019-06-24 22:16 ` Andrew Lunn [this message]
2019-06-24 15:10 ` [PATCH net-next v2 4/8] net: aquantia: make all files GPL-2.0-only Igor Russkikh
2019-06-24 22:16 ` Andrew Lunn
2019-06-24 15:10 ` [PATCH net-next v2 5/8] net: aquantia: added vlan offload related macros and functions Igor Russkikh
2019-06-24 15:10 ` [PATCH net-next v2 6/8] net: aquantia: adding fields and device features for vlan offload Igor Russkikh
2019-06-24 15:10 ` [PATCH net-next v2 7/8] net: aquantia: vlan offloads logic in datapath Igor Russkikh
2019-06-24 15:10 ` [PATCH net-next v2 8/8] net: aquantia: implement vlan offload configuration 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=20190624221620.GF31306@lunn.ch \
--to=andrew@lunn.ch \
--cc=Igor.Russkikh@aquantia.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.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).