From: Doug Ledford <dledford@redhat.com>
To: "Torvalds, Linus" <torvalds@linux-foundation.org>
Cc: linux-rdma <linux-rdma@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
"Gunthorpe, Jason" <jgg@ziepe.ca>
Subject: [GIT PULL] Please pull rdma.git
Date: Mon, 29 Apr 2019 12:28:57 -0400 [thread overview]
Message-ID: <48cbd548d153d1d2a1cf6c4f2127a6cef5d55deb.camel@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1106 bytes --]
Hi Linus,
As per the thread on our last pull request, this is the two line build
fix for s390 and mips.
The following changes since commit
2557fabd6e29f349bfa0ac13f38ac98aa5eafc74:
RDMA/hns: Bugfix for mapping user db (2019-04-25 10:40:04 -0300)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma.git tags/for-
linus
for you to fetch changes up to d79a26b99f5f40db6863b1973750fd1d134d99b4:
RDMA/uverbs: Fix compilation error on s390 and mips platforms (2019-
04-29 11:47:55 -0400)
----------------------------------------------------------------
Pull request for 5.1-rc
- Build fix for the last pull request on s390
----------------------------------------------------------------
Leon Romanovsky (1):
RDMA/uverbs: Fix compilation error on s390 and mips platforms
drivers/infiniband/core/uverbs_main.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
Doug Ledford <dledford@redhat.com>
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 --]
next reply other threads:[~2019-04-29 16:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-29 16:28 Doug Ledford [this message]
2019-04-29 16:48 ` [GIT PULL] Please pull rdma.git Linus Torvalds
2019-04-29 17:13 ` Doug Ledford
2019-04-29 18:00 ` Leon Romanovsky
2019-04-29 18:17 ` Doug Ledford
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=48cbd548d153d1d2a1cf6c4f2127a6cef5d55deb.camel@redhat.com \
--to=dledford@redhat.com \
--cc=jgg@ziepe.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=torvalds@linux-foundation.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