From: Gal Pressman <galpress@amazon.com>
To: Jason Gunthorpe <jgg@ziepe.ca>,
Doug Ledford <dledford@redhat.com>,
Christoph Hellwig <hch@lst.de>
Cc: <linux-rdma@vger.kernel.org>
Subject: Problem in for-next commit 6ffedfe3ae38 ("IB/umem: remove the dmasync argument to ib_umem_get")
Date: Sun, 17 Nov 2019 16:30:30 +0200 [thread overview]
Message-ID: <1fda84d9-a4b7-4d3f-fec2-82344e1cb220@amazon.com> (raw)
FYI, looks like something got messed up in commit 6ffedfe3ae38 ("IB/umem: remove
the dmasync argument to ib_umem_get"), it brings back the entire deleted
iwch_provider.c file.
next reply other threads:[~2019-11-17 14:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-17 14:30 Gal Pressman [this message]
2019-11-17 14:39 ` Problem in for-next commit 6ffedfe3ae38 ("IB/umem: remove the dmasync argument to ib_umem_get") 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=1fda84d9-a4b7-4d3f-fec2-82344e1cb220@amazon.com \
--to=galpress@amazon.com \
--cc=dledford@redhat.com \
--cc=hch@lst.de \
--cc=jgg@ziepe.ca \
--cc=linux-rdma@vger.kernel.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).