linux-rdma.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Drung <benjamin.drung-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
To: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	Jason Gunthorpe <jgg-uk2M96/98Pc@public.gmane.org>
Cc: Linux RDMA Mailing List
	<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: rdma-core_15-1_amd64.changes ACCEPTED into unstable
Date: Tue, 14 Nov 2017 11:51:01 +0100	[thread overview]
Message-ID: <1510656661.4026.23.camel@profitbricks.com> (raw)
In-Reply-To: <20171114072056.GP18825-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 1102 bytes --]

Am Dienstag, den 14.11.2017, 09:20 +0200 schrieb Leon Romanovsky:
> On Mon, Nov 13, 2017 at 07:37:11PM -0700, Jason Gunthorpe wrote:
> > Great news! Good job!
> 
> Thanks a lot.

Yeah, finally \o/

Now it is also synced to Ubuntu 18.04 (bionic):
https://launchpad.net/ubuntu/+source/rdma-core

Some builds fail. Reasons:

* Non-Linux architectures: One package is marked as architechture "any"
instead of "linux-any". Thus the builds are tried on non-Linux archs.
Expect a patch to come.

* Architecture NOT able to do coherent DMA: Some providers will be
disabled and the install target fail to install the missing providers.

* valgrind is not available on some archs: Can we drop valgrind for
those archs?

-- 
Benjamin Drung
System Developer
Debian & Ubuntu Developer

ProfitBricks GmbH
Greifswalder Str. 207
D - 10405 Berlin

Email: benjamin.drung-EIkl63zCoXaH+58JC4qpiA@public.gmane.org
URL: https://www.profitbricks.de

Sitz der Gesellschaft: Berlin
Registergericht: Amtsgericht Charlottenburg, HRB 125506 B
Geschäftsführer: Achim Weiss, Matthias Steinberg

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

  parent reply	other threads:[~2017-11-14 10:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-13 23:00 rdma-core_15-1_amd64.changes ACCEPTED into unstable, unstable Debian FTP Masters
     [not found] ` <E1eENiD-000EaM-BG-zBwJlDMnrE7yUObV3Cmqeti2O/JbrIOy@public.gmane.org>
2017-11-14  2:37   ` Jason Gunthorpe
     [not found]     ` <20171114023711.GA22633-uk2M96/98Pc@public.gmane.org>
2017-11-14  7:20       ` Leon Romanovsky
     [not found]         ` <20171114072056.GP18825-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-11-14 10:51           ` Benjamin Drung [this message]
     [not found]             ` <1510656661.4026.23.camel-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
2017-11-14 11:01               ` rdma-core_15-1_amd64.changes ACCEPTED into unstable Leon Romanovsky
2017-11-14 18:47               ` Jason Gunthorpe
     [not found]                 ` <20171114184719.GC4263-uk2M96/98Pc@public.gmane.org>
2017-11-14 18:58                   ` Benjamin Drung
     [not found]                     ` <1510685923.4026.41.camel-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
2017-11-17 23:31                       ` Jason Gunthorpe

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=1510656661.4026.23.camel@profitbricks.com \
    --to=benjamin.drung-eikl63zcoxah+58jc4qpia@public.gmane.org \
    --cc=jgg-uk2M96/98Pc@public.gmane.org \
    --cc=leon-DgEjT+Ai2ygdnm+yROfE0A@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 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).