From: Jason Gunthorpe <jgg@ziepe.ca>
To: Corentin Labbe <clabbe@baylibre.com>
Cc: dledford@redhat.com, hal.rosenstock@gmail.com,
infinipath@intel.com, sean.hefty@intel.com,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org
Subject: Re: [PATCH] IB/qib: remove qib_keys.c
Date: Sun, 28 Jan 2018 14:13:12 -0700 [thread overview]
Message-ID: <20180128211312.GC26025@ziepe.ca> (raw)
In-Reply-To: <1517152135-24942-1-git-send-email-clabbe@baylibre.com>
On Sun, Jan 28, 2018 at 03:08:55PM +0000, Corentin Labbe wrote:
> qib_keys.c was left uncompilable in commit 7c2e11fe2dbe ("IB/qib: Remove qp and mr functionality from qib")
> Since nothing need it, remove it from tree.
>
> Signed-off-by: Corentin Labbe <clabbe@baylibre.com>
> drivers/infiniband/hw/qib/qib_keys.c | 235 -----------------------------------
> 1 file changed, 235 deletions(-)
> delete mode 100644 drivers/infiniband/hw/qib/qib_keys.c
Applied to for-next, thanks
Jason
prev parent reply other threads:[~2018-01-28 21:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-28 15:08 [PATCH] IB/qib: remove qib_keys.c Corentin Labbe
2018-01-28 21:13 ` Jason Gunthorpe [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=20180128211312.GC26025@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=clabbe@baylibre.com \
--cc=dledford@redhat.com \
--cc=hal.rosenstock@gmail.com \
--cc=infinipath@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=sean.hefty@intel.com \
/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