From: David Miller <davem@davemloft.net>
To: igor.russkikh@aquantia.com
Cc: netdev@vger.kernel.org, darcari@redhat.com, pavel.belous@aquantia.com
Subject: Re: [PATCH net-next v3 0/5] net: aquantia: various ethtool ops implementation
Date: Tue, 03 Jul 2018 23:24:05 +0900 (KST) [thread overview]
Message-ID: <20180703.232405.355892924699732095.davem@davemloft.net> (raw)
In-Reply-To: <cover.1530537192.git.igor.russkikh@aquantia.com>
From: Igor Russkikh <igor.russkikh@aquantia.com>
Date: Mon, 2 Jul 2018 17:03:34 +0300
> In this patchset Anton Mikaev and I added some useful ethtool operations:
> - ring size changes
> - link renegotioation
> - flow control management
>
> The patch also improves init/deinit sequence.
>
> V3 changes:
> - After review and analysis it is clear that rtnl lock (which is
> captured by default on ethtool ops) is enough to secure possible
> overlapping of dev open/close. Thus, just dropping internal mutex.
>
> V2 changes:
> - using mutex to secure simultaneous dev close/open
> - using state var to store/restore dev state
Series applied.
prev parent reply other threads:[~2018-07-03 14:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-02 14:03 [PATCH net-next v3 0/5] net: aquantia: various ethtool ops implementation Igor Russkikh
2018-07-02 14:03 ` [PATCH net-next v3 1/5] net: aquantia: Ethtool based ring size configuration Igor Russkikh
2018-07-02 14:03 ` [PATCH net-next v3 2/5] net: aquantia: Improve adapter init/deinit logic Igor Russkikh
2018-07-02 14:03 ` [PATCH net-next v3 3/5] net: aquantia: Implement rx/tx flow control ethtools callback Igor Russkikh
2018-07-02 14:03 ` [PATCH net-next v3 4/5] net: aquantia: Add renegotiate ethtool operation support Igor Russkikh
2018-07-02 14:03 ` [PATCH net-next v3 5/5] net: aquantia: bump driver version Igor Russkikh
2018-07-03 14:24 ` David Miller [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=20180703.232405.355892924699732095.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=darcari@redhat.com \
--cc=igor.russkikh@aquantia.com \
--cc=netdev@vger.kernel.org \
--cc=pavel.belous@aquantia.com \
/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