From: Changqing Li <changqing.li@windriver.com>
To: Sunil Kumar Kori <skori@marvell.com>,
Jerin Jacob <jerinj@marvell.com>,
David Marchand <david.marchand@redhat.com>,
"thomas@monjalon.net" <thomas@monjalon.net>,
Stephen Hemminger <stephen@networkplumber.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [EXTERNAL] Re: |FAILURE| pw153190 [PATCH V3] Add new tracepoint function for type time_t
Date: Wed, 28 May 2025 16:14:27 +0800 [thread overview]
Message-ID: <936dd1eb-07a0-466d-bc25-48ba98def59b@windriver.com> (raw)
In-Reply-To: <CO6PR18MB3860EF5F3CA54B85A0E73CCCB467A@CO6PR18MB3860.namprd18.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1948 bytes --]
Hi,
Just kindly remind, with the help of Jerin's comment, I had just send
a V4 version yesterday.
Here is the patch link:
https://patches.dpdk.org/project/dpdk/patch/20250527120404.2027529-1-changqing.li@windriver.com/
Regards
Sandy
On 5/28/25 16:06, Sunil Kumar Kori wrote:
> CAUTION: This email comes from a non Wind River email account!
> Do not click links or open attachments unless you recognize the sender and know the content is safe.
>
> Please mark this version as superseded as new version is available.
>
> Thanks
> Sunil Kumar Kori
>
>> -----Original Message-----
>> From: Jerin Jacob<jerinj@marvell.com>
>> Sent: Thursday, May 8, 2025 7:24 PM
>> To: Changqing Li<changqing.li@windriver.com>; David Marchand
>> <david.marchand@redhat.com>; Sunil Kumar Kori<skori@marvell.com>;
>> thomas@monjalon.net; Stephen Hemminger<stephen@networkplumber.org>
>> Cc:dev@dpdk.org
>> Subject: RE: [EXTERNAL] Re: |FAILURE| pw153190 [PATCH V3] Add new tracepoint
>> function for type time_t
>>
>>> I'm new to this project, and have no clue about the failure, could
>>> experts at this project provide
>>>
>>> some help about the following failure?
>>>
>>> + sudo babeltrace
>>> /home/runner/work/dpdk/dpdk/build/app/test/suites/rte-2025-04-30-AM-02
>>> -
>>> 25-21
>>>
>>> Error: at line 2819: token "time_t": syntax error, unexpected
>>> IDENTIFIER
>>> Error: Error creating AST
>>>
>>>
>>> I think this time_t type you added is not described in CTF.
>>> Have a look at 2114521cff91 ("trace: fix size_t field emitter").
>>>
>>> Copying the trace framework maintainers who will have a better idea.
>>
>>
>> time_t is not defined in CTF spec. See
>> https://diamon.org/ctf/v1.8.3/#specification.
>> You can create new type using typealias with integer or structure as backend
>> type. See meta_data_type_emit() in DPDK code base where we created new
>> types.
>>
[-- Attachment #2: Type: text/html, Size: 3423 bytes --]
next prev parent reply other threads:[~2025-05-28 8:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-29 3:00 [PATCH] " changqing.li
2025-04-29 3:04 ` [PATCH V2] " changqing.li
2025-04-30 1:34 ` [PATCH V3] " changqing.li
[not found] ` <20250430024403.2690306-1-robot@bytheb.org>
2025-04-30 5:21 ` |FAILURE| pw153190 " Changqing Li
2025-05-05 13:56 ` David Marchand
2025-05-07 2:21 ` Changqing Li
2025-05-08 13:53 ` [EXTERNAL] " Jerin Jacob
2025-05-28 8:06 ` Sunil Kumar Kori
2025-05-28 8:14 ` Changqing Li [this message]
2025-05-27 12:04 ` [PATCH V4] " changqing.li
2025-05-28 16:14 ` [EXTERNAL] " Sunil Kumar Kori
2025-06-09 13:36 ` Thomas Monjalon
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=936dd1eb-07a0-466d-bc25-48ba98def59b@windriver.com \
--to=changqing.li@windriver.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=skori@marvell.com \
--cc=stephen@networkplumber.org \
--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).