public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Benjamin Drung <benjamin.drung-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH rdma-core 0/3] Debian packaging fixes
Date: Tue, 14 Nov 2017 20:33:59 +0200	[thread overview]
Message-ID: <20171114183359.GE18825@mtr-leonro.local> (raw)
In-Reply-To: <20171114113330.2715-1-benjamin.drung-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>

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

On Tue, Nov 14, 2017 at 12:33:27PM +0100, Benjamin Drung wrote:
> rdma-core 15-1 was accepted in Debian unstable and it failed to build on some
> architectures:
> https://buildd.debian.org/status/package.php?p=rdma-core
>
> This series tries to address some.
>

Thanks, applied

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      parent reply	other threads:[~2017-11-14 18:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-14 11:33 [PATCH rdma-core 0/3] Debian packaging fixes Benjamin Drung
     [not found] ` <20171114113330.2715-1-benjamin.drung-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
2017-11-14 11:33   ` [PATCH rdma-core 1/3] debian: Do not build ibacm for non-Linux architectures Benjamin Drung
2017-11-14 11:33   ` [PATCH rdma-core 2/3] debian: Do not require valgrind if not available Benjamin Drung
2017-11-14 11:33   ` [PATCH rdma-core 3/3] debian: Update changelog to include Debian upload Benjamin Drung
     [not found]     ` <20171114113330.2715-4-benjamin.drung-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
2017-11-14 20:28       ` Jason Gunthorpe
     [not found]         ` <20171114202823.GQ4263-uk2M96/98Pc@public.gmane.org>
2017-11-14 20:34           ` Benjamin Drung
     [not found]             ` <1510691646.4026.50.camel-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
2017-11-14 20:42               ` Jason Gunthorpe
     [not found]                 ` <20171114204244.GU4263-uk2M96/98Pc@public.gmane.org>
2017-11-15  9:23                   ` Benjamin Drung
     [not found]                     ` <1510737831.4026.59.camel-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
2017-11-17 23:41                       ` Jason Gunthorpe
2017-11-14 18:33   ` Leon Romanovsky [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=20171114183359.GE18825@mtr-leonro.local \
    --to=leon-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
    --cc=benjamin.drung-EIkl63zCoXaH+58JC4qpiA@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