DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Keller, Jacob E" <jacob.e.keller@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>,
	"Richardson, Bruce" <bruce.richardson@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"Hore, Soumyadeep" <soumyadeep.hore@intel.com>
Subject: RE: [PATCH] Revert "net/iavf: fix check for PF Rx timestamp support"
Date: Mon, 1 Dec 2025 22:51:55 +0000	[thread overview]
Message-ID: <CO1PR11MB5089B6E1F71F2726FACED400D6DBA@CO1PR11MB5089.namprd11.prod.outlook.com> (raw)
In-Reply-To: <3833052.e9J7NaK4W3@thomas>



> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Friday, November 28, 2025 2:56 AM
> To: Richardson, Bruce <bruce.richardson@intel.com>
> Cc: dev@dpdk.org; Keller, Jacob E <jacob.e.keller@intel.com>; Hore, Soumyadeep
> <soumyadeep.hore@intel.com>
> Subject: Re: [PATCH] Revert "net/iavf: fix check for PF Rx timestamp support"
> 
> 27/11/2025 10:25, Hore, Soumyadeep:
> > This reverts commit d21c2fe6e5a1ef1e7cc9490f54f359db1cfd5283.
> > While fixing an issue with enabling Rx timestamping on PFs which don't report
> Rx timestamping, the offending commit broke PFs which do support Rx
> timestamping.
> >
> > Fixes: d21c2fe6e5a1 ("net/iavf: fix check for PF Rx timestamp support")
> >
> > Suggested-by: Jacob Keller <jacob.e.keller@intel.com>
> > Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> >
> > Acked-by: Soumyadeep Hore <soumyadeep.hore@intel.com>
> 
> Applied, thanks.
> 

Thanks!

      reply	other threads:[~2025-12-01 22:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-26 16:59 Bruce Richardson
2025-11-27  9:25 ` Hore, Soumyadeep
2025-11-28 10:55   ` Thomas Monjalon
2025-12-01 22:51     ` Keller, Jacob E [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=CO1PR11MB5089B6E1F71F2726FACED400D6DBA@CO1PR11MB5089.namprd11.prod.outlook.com \
    --to=jacob.e.keller@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=soumyadeep.hore@intel.com \
    --cc=thomas@monjalon.net \
    /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).