From: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Jason Gunthorpe <jgg-uk2M96/98Pc@public.gmane.org>,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: Jason Gunthorpe <jgg-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Subject: Re: [PATCH rdma-core 0/3] Fixes for cbuild and travis
Date: Wed, 17 Jan 2018 10:49:49 -0500 [thread overview]
Message-ID: <1516204189.3403.256.camel@redhat.com> (raw)
In-Reply-To: <20180115211347.5651-1-jgg-uk2M96/98Pc@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 997 bytes --]
On Mon, 2018-01-15 at 14:13 -0700, Jason Gunthorpe wrote:
> From: Jason Gunthorpe <jgg-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
>
> Fix the unconditional travis failures with the latest suse tumbleweed docker
> images
>
> Fix perplexing travis failures with no output from sparse.
>
> Use clang 5.0
>
> This is a PR:
>
> https://github.com/linux-rdma/rdma-core/pull/283
>
> Jason Gunthorpe (3):
> cbuild: Support distros that only ship python3
> travis: Do not loose ninja output if ninja fails during sparse
> travis: Use clang-5.0
>
> .travis.yml | 6 +++---
> buildlib/cbuild | 16 ++++++++++------
> buildlib/travis-build | 10 +++++-----
> 3 files changed, 18 insertions(+), 14 deletions(-)
>
This was merged yesterday. I forgot to email the list, sorry.
--
Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
GPG KeyID: B826A3330E572FDD
Key fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2018-01-17 15:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-15 21:13 [PATCH rdma-core 0/3] Fixes for cbuild and travis Jason Gunthorpe
[not found] ` <20180115211347.5651-1-jgg-uk2M96/98Pc@public.gmane.org>
2018-01-15 21:13 ` [PATCH rdma-core 1/3] cbuild: Support distros that only ship python3 Jason Gunthorpe
[not found] ` <20180115211347.5651-2-jgg-uk2M96/98Pc@public.gmane.org>
2018-01-17 16:25 ` Nicolas Morey-Chaisemartin
[not found] ` <f75a3cd5-9763-0b4c-5e99-0565023967e4-l3A5Bk7waGM@public.gmane.org>
2018-01-17 16:28 ` Jason Gunthorpe
[not found] ` <20180117162858.GA3788-uk2M96/98Pc@public.gmane.org>
2018-01-17 16:31 ` Nicolas Morey-Chaisemartin
2018-01-15 21:13 ` [PATCH rdma-core 2/3] travis: Do not loose ninja output if ninja fails during sparse Jason Gunthorpe
2018-01-15 21:13 ` [PATCH rdma-core 3/3] travis: Use clang-5.0 Jason Gunthorpe
2018-01-17 15:49 ` Doug Ledford [this message]
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=1516204189.3403.256.camel@redhat.com \
--to=dledford-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=jgg-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=jgg-uk2M96/98Pc@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.