From: Bruce Richardson <bruce.richardson@intel.com>
To: Soumyadeep Hore <soumyadeep.hore@intel.com>
Cc: <dev@dpdk.org>, <rajesh3.kumar@intel.com>,
<aman.deep.singh@intel.com>, <manoj.kumar.subbarao@intel.com>,
<ciara.loftus@intel.com>, <stable@dpdk.org>
Subject: Re: [PATCH v2 3/3] doc: update TxPP documentation
Date: Tue, 4 Nov 2025 11:41:11 +0000 [thread overview]
Message-ID: <aQnmV9s7VRfOtyQ-@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <20251030173304.260209-4-soumyadeep.hore@intel.com>
On Thu, Oct 30, 2025 at 01:33:04PM -0400, Soumyadeep Hore wrote:
> TxPP feature works only when DPDK library is compiled with
> PTP feature enabled and application is run on PF.
>
> Fixes: 0b6ff09a1f19 ("net/intel: support Tx packet pacing for E830")
> Cc: stable@dpdk.org
>
> Signed-off-by: Soumyadeep Hore <soumyadeep.hore@intel.com>
> ---
Acked-by: Bruce Richardson <bruce.richardson@intel.com>
prev parent reply other threads:[~2025-11-04 11:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251027182801.191295-1-soumyadeep.hore@intel.com>
2025-10-27 18:27 ` [PATCH v1 1/3] net/ice: restrict testpmd to scalar path for TxPP Soumyadeep Hore
2025-10-29 9:30 ` Loftus, Ciara
2025-10-27 18:28 ` [PATCH v1 2/3] net/ice: fix PTP clock corruption with TxPP Soumyadeep Hore
2025-10-29 17:11 ` Bruce Richardson
2025-10-27 18:28 ` [PATCH v1 3/3] doc: update TxPP documentation Soumyadeep Hore
[not found] ` <20251030173304.260209-1-soumyadeep.hore@intel.com>
2025-10-30 17:33 ` [PATCH v2 1/3] net/ice: restrict ice PMD to scalar path for TxPP Soumyadeep Hore
2025-11-03 10:25 ` Loftus, Ciara
2025-10-30 17:33 ` [PATCH v2 2/3] net/ice: fix PTP clock corruption with TxPP Soumyadeep Hore
2025-11-04 11:32 ` Bruce Richardson
2025-10-30 17:33 ` [PATCH v2 3/3] doc: update TxPP documentation Soumyadeep Hore
2025-11-04 11:41 ` 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=aQnmV9s7VRfOtyQ-@bricha3-mobl1.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=aman.deep.singh@intel.com \
--cc=ciara.loftus@intel.com \
--cc=dev@dpdk.org \
--cc=manoj.kumar.subbarao@intel.com \
--cc=rajesh3.kumar@intel.com \
--cc=soumyadeep.hore@intel.com \
--cc=stable@dpdk.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).