patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: dpdk stable <stable@dpdk.org>
Subject: Re: please help backporting some patches to stable release 22.11.9
Date: Mon, 14 Jul 2025 09:11:47 -0700	[thread overview]
Message-ID: <20250714091147.0a373987@hermes.local> (raw)
In-Reply-To: <20250714151339.220149-1-luca.boccassi@gmail.com>

On Mon, 14 Jul 2025 16:13:36 +0100
luca.boccassi@gmail.com wrote:

> 4e12258d78  Stephen Hemminger latencystats: fix receive sample race

Skip this, I don't think anyone uses it. There were several bugs there
that would give bogus data.

  reply	other threads:[~2025-07-14 16:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-14 15:13 luca.boccassi
2025-07-14 16:11 ` Stephen Hemminger [this message]
2025-07-15  6:56 ` David Marchand
  -- strict thread matches above, loose matches on Subject: below --
2025-06-30 12:29 luca.boccassi
2025-06-30 19:15 ` Pathak, Pravin
2025-06-12 21:15 luca.boccassi

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=20250714091147.0a373987@hermes.local \
    --to=stephen@networkplumber.org \
    --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).