From: Jakub Kicinski <kuba@kernel.org>
To: Jiawen Wu <jiawenwu@trustnetic.com>
Cc: davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
linux@armlinux.org.uk, andrew@lunn.ch, netdev@vger.kernel.org,
mengyuanlou@net-swift.com
Subject: Re: [PATCH net-next v5 5/8] net: wangxun: add ethtool_ops for ring parameters
Date: Fri, 15 Dec 2023 18:36:16 -0800 [thread overview]
Message-ID: <20231215183616.0114c73b@kernel.org> (raw)
In-Reply-To: <20231214025456.1387175-6-jiawenwu@trustnetic.com>
On Thu, 14 Dec 2023 10:54:53 +0800 Jiawen Wu wrote:
> + if (ring->rx_mini_pending || ring->rx_jumbo_pending)
> + return -EOPNOTSUPP;
Kernel already checks request is within what's reported as max.
--
pw-bot: cr
next prev parent reply other threads:[~2023-12-16 2:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-14 2:54 [PATCH net-next v5 0/8] Implement more ethtool_ops for Wangxun Jiawen Wu
2023-12-14 2:54 ` [PATCH net-next v5 1/8] net: libwx: add phylink to libwx Jiawen Wu
2023-12-14 2:54 ` [PATCH net-next v5 2/8] net: txgbe: use phylink bits added in libwx Jiawen Wu
2023-12-14 2:54 ` [PATCH net-next v5 3/8] net: ngbe: convert phylib to phylink Jiawen Wu
2023-12-14 2:54 ` [PATCH net-next v5 4/8] net: wangxun: add flow control support Jiawen Wu
2023-12-14 2:54 ` [PATCH net-next v5 5/8] net: wangxun: add ethtool_ops for ring parameters Jiawen Wu
2023-12-16 2:36 ` Jakub Kicinski [this message]
2023-12-14 2:54 ` [PATCH net-next v5 6/8] net: wangxun: add coalesce options support Jiawen Wu
2023-12-16 2:38 ` Jakub Kicinski
2023-12-22 8:20 ` Jiawen Wu
2023-12-14 2:54 ` [PATCH net-next v5 7/8] net: wangxun: add ethtool_ops for channel number Jiawen Wu
2023-12-16 2:41 ` Jakub Kicinski
2023-12-14 2:54 ` [PATCH net-next v5 8/8] net: wangxun: add ethtool_ops for msglevel Jiawen Wu
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=20231215183616.0114c73b@kernel.org \
--to=kuba@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jiawenwu@trustnetic.com \
--cc=linux@armlinux.org.uk \
--cc=mengyuanlou@net-swift.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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.