From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw151088 [RFC 10/10] eal: deprecate weak symbols
Date: Fri, 7 Feb 2025 04:29:24 -0500 [thread overview]
Message-ID: <20250207092924.1215394-1-robot@bytheb.org> (raw)
In-Reply-To: <20250207083252.3131588-11-david.marchand@redhat.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/151088/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/13196318075
next prev parent reply other threads:[~2025-02-07 9:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250207083252.3131588-11-david.marchand@redhat.com>
2025-02-07 7:59 ` |SUCCESS| pw151079-151088 " qemudev
2025-02-07 8:04 ` qemudev
2025-02-07 9:29 ` 0-day Robot [this message]
2025-02-07 11:29 ` |SUCCESS| pw151079-151088 [PATCH] [RFC,10/10] eal: deprecate weak sy dpdklab
2025-02-07 11:45 ` dpdklab
2025-02-07 11:50 ` dpdklab
2025-02-07 12:17 ` |PENDING| " dpdklab
2025-02-07 12:25 ` |SUCCESS| " dpdklab
2025-02-07 12:27 ` dpdklab
2025-02-07 12:28 ` |PENDING| " dpdklab
2025-02-07 13:13 ` |SUCCESS| " dpdklab
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=20250207092924.1215394-1-robot@bytheb.org \
--to=robot@bytheb.org \
--cc=test-report@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).