patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Kevin Traynor <ktraynor@redhat.com>
To: David Marchand <david.marchand@redhat.com>
Cc: stable@dpdk.org, Sunil Kumar Kori <skori@marvell.com>,
	Jerin Jacob <jerinj@marvell.com>
Subject: Re: [PATCH] trace: fix metadata dump
Date: Tue, 29 Nov 2022 11:55:21 +0000	[thread overview]
Message-ID: <f1afdd53-927d-bd47-84d3-ce9157d085ad@redhat.com> (raw)
In-Reply-To: <5c3b05a6-696d-5dfc-4b52-f21bc948fad9@redhat.com>

On 28/11/2022 10:12, Kevin Traynor wrote:
> On 28/11/2022 09:27, David Marchand wrote:
>> On Thu, Nov 24, 2022 at 9:12 AM David Marchand
>> <david.marchand@redhat.com> wrote:
>>>
>>> [ upstream commit d4cbbee345e2ea1126f3f43cbc1fedaf1245feb0 ]
>>>
>>> The API does not describe that metadata dump is conditioned to enabling
>>> any trace points.
>>>
>>> While at it, merge dump unit tests into the generic trace_autotest to
>>> enhance coverage.
>>>
>>> Fixes: f6b2d65dcd5d ("trace: implement debug dump")
>>>
>>> Signed-off-by: David Marchand <david.marchand@redhat.com>
>>> Acked-by: Sunil Kumar Kori <skori@marvell.com>
>>
>> It is meant for 21.11, but I forgot to make it clear in the title prefix.
>> Do you want me to resend?
>>
>>
> 
> No need. It is already pushed to 21.11-staging branch. If any of the
> other maintainers spot it in the mailing list, they will be able to read
> the clarification in the thead. Thanks.

Pushed to 21.11 branch now. Thanks.


      reply	other threads:[~2022-11-29 11:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-24  8:12 David Marchand
2022-11-28  9:27 ` David Marchand
2022-11-28 10:12   ` Kevin Traynor
2022-11-29 11:55     ` Kevin Traynor [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=f1afdd53-927d-bd47-84d3-ce9157d085ad@redhat.com \
    --to=ktraynor@redhat.com \
    --cc=david.marchand@redhat.com \
    --cc=jerinj@marvell.com \
    --cc=skori@marvell.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).