From: <sameehj@amazon.com>
To: <davem@davemloft.net>, <netdev@vger.kernel.org>
Cc: Sameeh Jubran <sameehj@amazon.com>, <dwmw@amazon.com>,
<zorik@amazon.com>, <matua@amazon.com>, <saeedb@amazon.com>,
<msw@amazon.com>, <aliguori@amazon.com>, <nafea@amazon.com>,
<gtzalik@amazon.com>, <netanel@amazon.com>, <alisaidi@amazon.com>,
<benh@amazon.com>, <akiyano@amazon.com>
Subject: [PATCH V2 net-next 0/5] Introduce ethtool's set_channels
Date: Thu, 19 Sep 2019 17:02:19 +0300 [thread overview]
Message-ID: <20190919140224.9137-1-sameehj@amazon.com> (raw)
From: Sameeh Jubran <sameehj@amazon.com>
Difference from v1:
* Dropped the print from patch 0002 - "net: ena: multiple queue creation
related cleanups" as requested by David Miller
Sameeh Jubran (5):
net: ena: change num_queues to num_io_queues for clarity and
consistency
net: ena: multiple queue creation related cleanups
net: ena: make ethtool -l show correct max number of queues
net: ena: remove redundant print of number of queues
net: ena: ethtool: support set_channels callback
drivers/net/ethernet/amazon/ena/ena_ethtool.c | 37 ++--
drivers/net/ethernet/amazon/ena/ena_netdev.c | 160 ++++++++++--------
drivers/net/ethernet/amazon/ena/ena_netdev.h | 14 +-
3 files changed, 121 insertions(+), 90 deletions(-)
--
2.17.1
next reply other threads:[~2019-09-19 14:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-19 14:02 sameehj [this message]
2019-09-19 14:02 ` [PATCH V2 net-next 1/5] net: ena: change num_queues to num_io_queues for clarity and consistency sameehj
2019-09-19 14:02 ` [PATCH V2 net-next 2/5] net: ena: multiple queue creation related cleanups sameehj
2019-09-19 14:02 ` [PATCH V2 net-next 3/5] net: ena: make ethtool -l show correct max number of queues sameehj
2019-09-19 14:02 ` [PATCH V2 net-next 4/5] net: ena: remove redundant print of " sameehj
2019-09-19 14:02 ` [PATCH V2 net-next 5/5] net: ena: ethtool: support set_channels callback sameehj
2019-09-19 14:36 ` [PATCH V2 net-next 0/5] Introduce ethtool's set_channels David Miller
-- strict thread matches above, loose matches on Subject: below --
2019-10-02 8:20 sameehj
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=20190919140224.9137-1-sameehj@amazon.com \
--to=sameehj@amazon.com \
--cc=akiyano@amazon.com \
--cc=aliguori@amazon.com \
--cc=alisaidi@amazon.com \
--cc=benh@amazon.com \
--cc=davem@davemloft.net \
--cc=dwmw@amazon.com \
--cc=gtzalik@amazon.com \
--cc=matua@amazon.com \
--cc=msw@amazon.com \
--cc=nafea@amazon.com \
--cc=netanel@amazon.com \
--cc=netdev@vger.kernel.org \
--cc=saeedb@amazon.com \
--cc=zorik@amazon.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.