linux-rdma.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: owner-61a8vm9lEZVf4u+23C9RwQ@public.gmane.org (Debian Bug Tracking System)
To: Adrian Bunk <bunk-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Processed: libibverbs-dev no longer ships infiniband/driver.h
Date: Wed, 15 Nov 2017 13:12:05 +0000	[thread overview]
Message-ID: <handler.s.B.15107514116787.transcript@bugs.debian.org> (raw)
In-Reply-To: 151075140461.17370.2844187627354872362.reportbug@localhost

Processing control commands:

> affects -1 libibverbs-dev src:librdmacm src:libcxgb3 src:libmlx4 src:libipathverbs src:libmlx5 src:libibcm src:libmthca src:libnes src:libfabric
Bug #881814 [src:rdma-core] libibverbs-dev no longer ships infiniband/driver.h
Added indication that 881814 affects libibverbs-dev, src:librdmacm, src:libcxgb3, src:libmlx4, src:libipathverbs, src:libmlx5, src:libibcm, src:libmthca, src:libnes, and src:libfabric

-- 
881814: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881814
Debian Bug Tracking System
Contact owner-61a8vm9lEZVf4u+23C9RwQ@public.gmane.org with problems
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

       reply	other threads:[~2017-11-15 13:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <151075140461.17370.2844187627354872362.reportbug@localhost>
2017-11-15 13:12 ` Debian Bug Tracking System [this message]
     [not found]   ` <handler.s.B.15107514116787.transcript-61a8vm9lEZVf4u+23C9RwQ@public.gmane.org>
2017-11-15 17:16     ` Processed: libibverbs-dev no longer ships infiniband/driver.h Jason Gunthorpe
     [not found] ` <20171115171657.GQ25894-uk2M96/98Pc@public.gmane.org>
2017-11-16 12:42   ` Bug#881814: " Benjamin Drung
2017-11-16 12:45     ` Processed: " Debian Bug Tracking System

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=handler.s.B.15107514116787.transcript@bugs.debian.org \
    --to=owner-61a8vm9lezvf4u+23c9rwq@public.gmane.org \
    --cc=bunk-8fiUuRrzOP0dnm+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).