From: Bruce Richardson <bruce.richardson@intel.com>
To: Kaiwen Deng <kaiwenx.deng@intel.com>
Cc: <dev@dpdk.org>, <stable@dpdk.org>,
Qi Zhang <qi.z.zhang@intel.com>,
Yaroslav Brustinov <ybrustin@cisco.com>
Subject: Re: [PATCH] net/intel: fix igb tx queue offloads capability
Date: Wed, 21 May 2025 11:17:46 +0100 [thread overview]
Message-ID: <aC2oSsbGSW8IlyAl@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <aC2nfWi3-27ibs61@bricha3-mobl1.ger.corp.intel.com>
On Wed, May 21, 2025 at 11:14:21AM +0100, Bruce Richardson wrote:
> patch prefix should be "net/e1000" rather than "net/intel". Even though
> patches are moved to an "intel" subdir, we still use the prefix of the
> actual driver name. As a general guideline, only use "intel" when modifying
> multiple intel drivers or the common directory.
>
> On Mon, Apr 14, 2025 at 04:53:52PM +0800, Kaiwen Deng wrote:
> > The igb driver assigns the tx port offload capability to the
> > tx queue offload capability.
> >
> > This commit will fix this issue.
> >
> > Fixes: daa3b0833f08 ("net/e1000: fix Tx offload capability typos")
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Kaiwen Deng <kaiwenx.deng@intel.com>
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
correction:
Acked-by: Bruce Richardson <bruce.richardson@intel.com>
>
> Applied to dpdk-next-net-intel.
>
> Thanks,
> /Bruce
prev parent reply other threads:[~2025-05-21 10:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-14 8:53 Kaiwen Deng
2025-04-28 15:20 ` Bruce Richardson
2025-05-07 8:59 ` Deng, KaiwenX
2025-05-21 10:14 ` Bruce Richardson
2025-05-21 10:14 ` Bruce Richardson
2025-05-21 10:17 ` Bruce Richardson [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=aC2oSsbGSW8IlyAl@bricha3-mobl1.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=kaiwenx.deng@intel.com \
--cc=qi.z.zhang@intel.com \
--cc=stable@dpdk.org \
--cc=ybrustin@cisco.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).