From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH 0/2] improve Travis coverage
Date: Mon, 17 Feb 2020 12:35:45 +0100 [thread overview]
Message-ID: <20200217113547.1889436-1-thomas@monjalon.net> (raw)
Remove some useless jobs and add more packages
to build more PMDs in Travis.
Warning: not tested yet! Hope Travis will do it well :-)
Thomas Monjalon (2):
ci: remove redundant configs disabling kmods
ci: enable more drivers in Travis builds
.travis.yml | 30 +++++-------------------------
1 file changed, 5 insertions(+), 25 deletions(-)
--
2.25.0
next reply other threads:[~2020-02-17 11:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-17 11:35 Thomas Monjalon [this message]
2020-02-17 11:35 ` [dpdk-dev] [PATCH 1/2] ci: remove redundant configs disabling kmods Thomas Monjalon
2020-02-17 14:06 ` Thomas Monjalon
2020-02-17 16:42 ` Aaron Conole
2020-02-17 16:46 ` Bruce Richardson
2020-02-17 18:00 ` Thomas Monjalon
2020-02-17 11:35 ` [dpdk-dev] [PATCH 2/2] ci: enable more drivers in Travis builds Thomas Monjalon
2020-02-17 18:00 ` Aaron Conole
2020-02-17 21:19 ` Thomas Monjalon
2020-02-17 21:38 ` Aaron Conole
2020-02-17 22:33 ` [dpdk-dev] [PATCH v2 0/2] improve Travis coverage Thomas Monjalon
2020-02-17 22:33 ` [dpdk-dev] [PATCH v2 1/2] ci: remove redundant configs disabling kmods Thomas Monjalon
2020-02-17 22:33 ` [dpdk-dev] [PATCH v2 2/2] ci: enable more drivers in Travis builds Thomas Monjalon
2020-02-18 21:20 ` [dpdk-dev] [PATCH v3 0/2] improve Travis coverage Thomas Monjalon
2020-02-18 21:20 ` [dpdk-dev] [PATCH v3 1/2] ci: remove redundant configs disabling kmods Thomas Monjalon
2020-02-18 21:20 ` [dpdk-dev] [PATCH v3 2/2] ci: enable more drivers in Travis builds Thomas Monjalon
2020-02-18 22:36 ` [dpdk-dev] [PATCH v3 0/2] improve Travis coverage David Marchand
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=20200217113547.1889436-1-thomas@monjalon.net \
--to=thomas@monjalon.net \
--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).