From: Jiri Pirko <jiri@resnulli.us>
To: Michal Wilczynski <michal.wilczynski@intel.com>
Cc: netdev@vger.kernel.org, alexandr.lobakin@intel.com,
jacob.e.keller@intel.com, jesse.brandeburg@intel.com,
przemyslaw.kitszel@intel.com, anthony.l.nguyen@intel.com,
kuba@kernel.org, ecree.xilinx@gmail.com
Subject: Re: [PATCH net-next v6 0/4] Implement devlink-rate API and extend it
Date: Tue, 18 Oct 2022 16:16:54 +0200 [thread overview]
Message-ID: <Y061VtBGHOaDK3y5@nanopsycho> (raw)
In-Reply-To: <20221018123543.1210217-1-michal.wilczynski@intel.com>
Tue, Oct 18, 2022 at 02:35:38PM CEST, michal.wilczynski@intel.com wrote:
>This is a follow up on:
>https://lore.kernel.org/netdev/20220915134239.1935604-1-michal.wilczynski@intel.com/
>
>This patch series implements devlink-rate for ice driver. Unfortunately
>current API isn't flexible enough for our use case, so there is a need to
>extend it. Some functions have been introduced to enable the driver to
>export current Tx scheduling configuration.
This is not enough to be said in the cover letter. You need to clearly
explain the motivation, what is the problem you are trying to solve and
describe the solution. Also, provide example commands and outputs here.
next prev parent reply other threads:[~2022-10-18 14:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 12:35 [PATCH net-next v6 0/4] Implement devlink-rate API and extend it Michal Wilczynski
2022-10-18 12:35 ` [PATCH net-next v6 1/4] devlink: Extend devlink-rate api with export functions and new params Michal Wilczynski
2022-10-18 14:08 ` Jiri Pirko
2022-10-18 15:13 ` Wilczynski, Michal
2022-10-18 12:35 ` [PATCH net-next v6 2/4] ice: Introduce new parameters in ice_sched_node Michal Wilczynski
2022-10-18 12:35 ` [PATCH net-next v6 3/4] ice: Implement devlink-rate API Michal Wilczynski
2022-10-18 12:35 ` [PATCH net-next v6 4/4] ice: Prevent DCB coexistence with Custom Tx scheduler Michal Wilczynski
2022-10-18 14:16 ` Jiri Pirko [this message]
2022-10-18 15:13 ` [PATCH net-next v6 0/4] Implement devlink-rate API and extend it Wilczynski, Michal
-- strict thread matches above, loose matches on Subject: below --
2022-10-18 12:37 Michal Wilczynski
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=Y061VtBGHOaDK3y5@nanopsycho \
--to=jiri@resnulli.us \
--cc=alexandr.lobakin@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=ecree.xilinx@gmail.com \
--cc=jacob.e.keller@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=kuba@kernel.org \
--cc=michal.wilczynski@intel.com \
--cc=netdev@vger.kernel.org \
--cc=przemyslaw.kitszel@intel.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).