netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Parav Pandit <parav@nvidia.com>
Cc: netdev@vger.kernel.org, dsahern@kernel.org,
	stephen@networkplumber.org, jiri@nvidia.com, shayd@nvidia.com
Subject: Re: [PATCH net] devlink: Fix setting max_io_eqs as the sole attribute
Date: Tue, 11 Jun 2024 15:10:30 +0000	[thread overview]
Message-ID: <171811863049.7300.38950884252778751.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240606043808.1330909-1-parav@nvidia.com>

Hello:

This patch was applied to iproute2/iproute2.git (main)
by Stephen Hemminger <stephen@networkplumber.org>:

On Thu, 6 Jun 2024 07:38:08 +0300 you wrote:
> dl_opts_put() function missed to consider IO eqs option flag.
> Due to this, when max_io_eqs setting is applied only when it
> is combined with other attributes such as roce/hw_addr.
> When max_io_eqs is the only attribute set, it missed to
> apply the attribute.
> 
> Fix it by adding the missing flag.
> 
> [...]

Here is the summary with links:
  - [net] devlink: Fix setting max_io_eqs as the sole attribute
    https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=c6c39f3c6da4

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2024-06-11 15:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-06  4:38 [PATCH net] devlink: Fix setting max_io_eqs as the sole attribute Parav Pandit
2024-06-06  4:40 ` Parav Pandit
2024-06-11 15:10 ` patchwork-bot+netdevbpf [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=171811863049.7300.38950884252778751.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=dsahern@kernel.org \
    --cc=jiri@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --cc=parav@nvidia.com \
    --cc=shayd@nvidia.com \
    --cc=stephen@networkplumber.org \
    /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).