From: Jakub Kicinski <kuba@kernel.org>
To: Mateusz Polchlopek <mateusz.polchlopek@intel.com>
Cc: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
jiri@resnulli.us, horms@kernel.org, przemyslaw.kitszel@intel.com,
andrew@lunn.ch, victor.raj@intel.com,
michal.wilczynski@intel.com, lukasz.czapnik@intel.com
Subject: Re: [Intel-wired-lan] [PATCH iwl-next v5 5/5] ice: Document tx_scheduling_layers parameter
Date: Mon, 4 Mar 2024 19:35:26 -0800 [thread overview]
Message-ID: <20240304193526.788ff854@kernel.org> (raw)
In-Reply-To: <20240228142054.474626-6-mateusz.polchlopek@intel.com>
On Wed, 28 Feb 2024 09:20:54 -0500 Mateusz Polchlopek wrote:
> From: Michal Wilczynski <michal.wilczynski@intel.com>
>
> New driver specific parameter 'tx_scheduling_layers' was introduced.
> Describe parameter in the documentation.
>
> Signed-off-by: Michal Wilczynski <michal.wilczynski@intel.com>
> Co-developed-by: Mateusz Polchlopek <mateusz.polchlopek@intel.com>
> Signed-off-by: Mateusz Polchlopek <mateusz.polchlopek@intel.com>
Acked-by: Jakub Kicinski <kuba@kernel.org>
prev parent reply other threads:[~2024-03-05 3:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-28 14:20 [Intel-wired-lan] [PATCH iwl-next v5 0/5] ice: Support 5 layer Tx scheduler topology Mateusz Polchlopek
2024-02-28 14:20 ` [Intel-wired-lan] [PATCH iwl-next v5 1/5] ice: Support 5 layer topology Mateusz Polchlopek
2024-02-28 14:20 ` [Intel-wired-lan] [PATCH iwl-next v5 2/5] ice: Adjust the VSI/Aggregator layers Mateusz Polchlopek
2024-02-28 14:20 ` [Intel-wired-lan] [PATCH iwl-next v5 3/5] ice: Enable switching default Tx scheduler topology Mateusz Polchlopek
2024-02-28 14:20 ` [Intel-wired-lan] [PATCH iwl-next v5 4/5] ice: Add tx_scheduling_layers devlink param Mateusz Polchlopek
2024-02-28 15:57 ` Jiri Pirko
2024-03-01 13:41 ` Mateusz Polchlopek
2024-03-01 15:46 ` Jiri Pirko
2024-03-05 12:31 ` Mateusz Polchlopek
2024-02-28 14:20 ` [Intel-wired-lan] [PATCH iwl-next v5 5/5] ice: Document tx_scheduling_layers parameter Mateusz Polchlopek
2024-03-05 3:35 ` Jakub Kicinski [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=20240304193526.788ff854@kernel.org \
--to=kuba@kernel.org \
--cc=andrew@lunn.ch \
--cc=horms@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jiri@resnulli.us \
--cc=lukasz.czapnik@intel.com \
--cc=mateusz.polchlopek@intel.com \
--cc=michal.wilczynski@intel.com \
--cc=netdev@vger.kernel.org \
--cc=przemyslaw.kitszel@intel.com \
--cc=victor.raj@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).