From: "Morten Brørup" <mb@smartsharesystems.com>
To: <ci@dpdk.org>
Cc: <dev@dpdk.org>
Subject: [dpdk-ci] Compilation error fixed by other patch
Date: Tue, 25 Jun 2019 21:43:35 +0200 [thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35B42985@smartserver.smartshare.dk> (raw)
Dear CI team,
Some patches failed compilation in CI due to unrelated compilation errors, which have now been fixed.
The fixes for the unrelated compilation errors are these:
https://patchwork.dpdk.org/patch/55085/
https://patchwork.dpdk.org/patch/55086/
A couple of my patches that failed compilation due to the above bugs, and would probably not fail now that they have been fixed, are:
https://patchwork.dpdk.org/patch/55168/
https://patchwork.dpdk.org/patch/55170/
How do I make Patchwork run the compilation tests on my two patches again, so they don't show up in the list as failing?
And a lot of other people's patches are similarly affected. Is there anything to do about that?
Med venlig hilsen / kind regards
- Morten Brørup
reply other threads:[~2019-06-25 19:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=98CBD80474FA8B44BF855DF32C47DC35B42985@smartserver.smartshare.dk \
--to=mb@smartsharesystems.com \
--cc=ci@dpdk.org \
--cc=dev@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).