All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stanislav Fomichev <stfomichev@gmail.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
	pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org,
	shuah@kernel.org, almasrymina@google.com, sdf@fomichev.me,
	joe@dama.to, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net-next v2 5/5] selftests: drv-net: ncdevmem: explicitly set HDS threshold to 0
Date: Mon, 25 Aug 2025 12:54:00 -0700	[thread overview]
Message-ID: <aKy_WJPrwNwOxOAc@mini-arch> (raw)
In-Reply-To: <20250825180447.2252977-6-kuba@kernel.org>

On 08/25, Jakub Kicinski wrote:
> Make sure we set HDS threshold to 0 if the device supports changing it.
> It's required for ZC.
> 
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> ---
> v2:
>  - split from previous patch
>  - only touch hds if device supports it

Acked-by: Stanislav Fomichev <sdf@fomichev.me>

  reply	other threads:[~2025-08-25 19:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-25 18:04 [PATCH net-next v2 0/5] selftests: drv-net: ncdevmem: fix error paths Jakub Kicinski
2025-08-25 18:04 ` [PATCH net-next v2 1/5] selftests: drv-net: ncdevmem: remove use of error() Jakub Kicinski
2025-08-25 18:04 ` [PATCH net-next v2 2/5] selftests: drv-net: ncdevmem: save IDs of flow rules we added Jakub Kicinski
2025-08-25 18:04 ` [PATCH net-next v2 3/5] selftests: drv-net: ncdevmem: restore old channel config Jakub Kicinski
2025-08-25 18:04 ` [PATCH net-next v2 4/5] selftests: drv-net: ncdevmem: restore original HDS setting before exiting Jakub Kicinski
2025-08-25 19:53   ` Stanislav Fomichev
2025-08-25 18:04 ` [PATCH net-next v2 5/5] selftests: drv-net: ncdevmem: explicitly set HDS threshold to 0 Jakub Kicinski
2025-08-25 19:54   ` Stanislav Fomichev [this message]
2025-08-27  1:00 ` [PATCH net-next v2 0/5] selftests: drv-net: ncdevmem: fix error paths patchwork-bot+netdevbpf

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=aKy_WJPrwNwOxOAc@mini-arch \
    --to=stfomichev@gmail.com \
    --cc=almasrymina@google.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=joe@dama.to \
    --cc=kuba@kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sdf@fomichev.me \
    --cc=shuah@kernel.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 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.