From: David Miller <davem@davemloft.net>
To: sameehj@amazon.com
Cc: netdev@vger.kernel.org, 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: Re: [PATCH V3 net-next 0/6]
Date: Mon, 07 Oct 2019 15:30:30 +0200 (CEST) [thread overview]
Message-ID: <20191007.153030.1870703252635689222.davem@davemloft.net> (raw)
In-Reply-To: <20191006123328.24210-1-sameehj@amazon.com>
From: <sameehj@amazon.com>
Date: Sun, 6 Oct 2019 15:33:22 +0300
> From: Sameeh Jubran <sameehj@amazon.com>
>
>
> Difference from v2:
> * ethtool's set/get channels: Switched to using combined instead of
> separate rx/tx
> * Fixed error handling in set_channels
> * Fixed indentation and cosmetic issues as requested by Jakub Kicinski
>
> Difference from v1:
> * Dropped the print from patch 0002 - "net: ena: multiple queue creation
> related cleanups" as requested by David Miller
Series applied.
prev parent reply other threads:[~2019-10-07 13:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-06 12:33 [PATCH V3 net-next 0/6] sameehj
2019-10-06 12:33 ` [PATCH V3 net-next 1/6] net: ena: change num_queues to num_io_queues for clarity and consistency sameehj
2019-10-06 12:33 ` [PATCH V3 net-next 2/6] net: ena: multiple queue creation related cleanups sameehj
2019-10-06 12:33 ` [PATCH V3 net-next 3/6] net: ena: ethtool: get_channels: use combined only sameehj
2019-10-06 12:33 ` [PATCH V3 net-next 4/6] net: ena: make ethtool -l show correct max number of queues sameehj
2019-10-06 12:33 ` [PATCH V3 net-next 5/6] net: ena: remove redundant print of " sameehj
2019-10-06 12:33 ` [PATCH V3 net-next 6/6] net: ena: ethtool: support set_channels callback sameehj
2019-10-07 13:30 ` 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=20191007.153030.1870703252635689222.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akiyano@amazon.com \
--cc=aliguori@amazon.com \
--cc=alisaidi@amazon.com \
--cc=benh@amazon.com \
--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=sameehj@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 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).