From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw114339 [PATCH v2] eal: change alloc_sz calculation which may cause unnecessarily allocation
Date: Thu, 28 Jul 2022 07:08:10 -0400 [thread overview]
Message-ID: <20220728110810.5877-1-robot@bytheb.org> (raw)
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/2752989037
next reply other threads:[~2022-07-28 11:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-28 11:08 0-day Robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-07-28 11:48 |SUCCESS| pw114339 [PATCH] [v2] " dpdklab
2022-07-28 11:28 dpdklab
2022-07-28 11:27 dpdklab
2022-07-28 11:18 dpdklab
2022-07-28 11:14 dpdklab
2022-07-28 11:02 dpdklab
2022-07-28 10:54 dpdklab
2022-07-28 10:47 dpdklab
2022-07-28 10:40 dpdklab
2022-07-28 10:27 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=20220728110810.5877-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).