DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Zhang Tengfei <zhtfdev@gmail.com>
Cc: Jiawen Wu <jiawenwu@trustnetic.com>,
	Zaiyu Wang <zaiyuwang@trustnetic.com>,
	dev@dpdk.org, stable@dpdk.org
Subject: Re: [PATCH] net/txgbe: fix FDIR devarg integer width
Date: Wed, 9 Sep 2026 13:42:05 -0700	[thread overview]
Message-ID: <20260909134205.7470b8df@phoenix.local> (raw)
In-Reply-To: <20260909173946.16645-1-zhtfdev@gmail.com>

On Thu, 10 Sep 2026 01:39:46 +0800
Zhang Tengfei <zhtfdev@gmail.com> wrote:

> txgbe_handle_devarg() stores a uint16_t through extra_args, but
> pballoc and drop_queue were u8. Setting pkt-filter-size overwrote
> the adjacent drop_queue default.
> 
> Fixes: 7e18be9beef2 ("net/txgbe: add device arguments for FDIR")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Zhang Tengfei <zhtfdev@gmail.com>
> ---

Applied to next-net.
Review saw another issue in devarg handling, sent followup patch for that.

      reply	other threads:[~2026-09-09 20:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-09 17:39 [PATCH] net/txgbe: fix FDIR devarg integer width Zhang Tengfei
2026-09-09 20:42 ` Stephen Hemminger [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=20260909134205.7470b8df@phoenix.local \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    --cc=jiawenwu@trustnetic.com \
    --cc=stable@dpdk.org \
    --cc=zaiyuwang@trustnetic.com \
    --cc=zhtfdev@gmail.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