public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel•org
To: Tony Nguyen <anthony.l.nguyen@intel•com>
Cc: davem@davemloft•net, kuba@kernel•org, pabeni@redhat•com,
	edumazet@google•com, netdev@vger•kernel.org,
	muhammad.husaini.zulkifli@intel•com, sasha.neftin@intel•com,
	vinicius.gomes@intel•com, horms@kernel•org, bcreeley@amd•com,
	naamax.meir@linux•intel.com
Subject: Re: [PATCH net v4] igc: Expose tx-usecs coalesce setting to user
Date: Thu, 21 Sep 2023 08:20:22 +0000	[thread overview]
Message-ID: <169528442281.5165.1476264155263100532.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230919170331.1581031-1-anthony.l.nguyen@intel.com>

Hello:

This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat•com>:

On Tue, 19 Sep 2023 10:03:31 -0700 you wrote:
> From: Muhammad Husaini Zulkifli <muhammad.husaini.zulkifli@intel•com>
> 
> When users attempt to obtain the coalesce setting using the
> ethtool command, current code always returns 0 for tx-usecs.
> This is because I225/6 always uses a queue pair setting, hence
> tx_coalesce_usecs does not return a value during the
> igc_ethtool_get_coalesce() callback process. The pair queue
> condition checking in igc_ethtool_get_coalesce() is removed by
> this patch so that the user gets information of the value of tx-usecs.
> 
> [...]

Here is the summary with links:
  - [net,v4] igc: Expose tx-usecs coalesce setting to user
    https://git.kernel.org/netdev/net/c/1703b2e0de65

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



      reply	other threads:[~2023-09-21  8:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-19 17:03 [PATCH net v4] igc: Expose tx-usecs coalesce setting to user Tony Nguyen
2023-09-21  8:20 ` 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=169528442281.5165.1476264155263100532.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel$(echo .)org \
    --cc=anthony.l.nguyen@intel$(echo .)com \
    --cc=bcreeley@amd$(echo .)com \
    --cc=davem@davemloft$(echo .)net \
    --cc=edumazet@google$(echo .)com \
    --cc=horms@kernel$(echo .)org \
    --cc=kuba@kernel$(echo .)org \
    --cc=muhammad.husaini.zulkifli@intel$(echo .)com \
    --cc=naamax.meir@linux$(echo .)intel.com \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=pabeni@redhat$(echo .)com \
    --cc=sasha.neftin@intel$(echo .)com \
    --cc=vinicius.gomes@intel$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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