All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: Marcin Zapolski <marcinx.a.zapolski@intel.com>,
	dev@dpdk.org, john.mcnamara@intel.com, marko.kovacevic@intel.com
Subject: Re: [dpdk-dev] [PATCH v2] doc: add code coverage report generation guide
Date: Mon, 12 Jun 2023 09:07:46 -0700	[thread overview]
Message-ID: <20230612090746.14f707ec@hermes.local> (raw)
In-Reply-To: <5114883.9lh0I85yue@thomas>

On Sun, 24 May 2020 23:22:57 +0200
Thomas Monjalon <thomas@monjalon.net> wrote:

> What is the status of this patch?
> There was no review.

Running unit tests was added to prog_guide documentation later.
This patch is no longer relevant.

      reply	other threads:[~2023-06-12 16:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-23  8:52 [dpdk-dev] [PATCH] doc: add code coverage report generation guide Marcin Zapolski
2019-09-23 12:15 ` [dpdk-dev] [PATCH v2] " Marcin Zapolski
2020-05-24 21:22   ` Thomas Monjalon
2023-06-12 16:07     ` 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=20230612090746.14f707ec@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.com \
    --cc=marcinx.a.zapolski@intel.com \
    --cc=marko.kovacevic@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.