From: Bart Van Assche <bvanassche@acm.org>
To: Leon Romanovsky <leon@kernel.org>,
Dennis Dalessandro <dennis.dalessandro@intel.com>
Cc: Sagi Grimberg <sagi@grimberg.me>,
Jason Gunthorpe <jgg@mellanox.com>,
Israel Rukshin <israelr@mellanox.com>,
linux-rdma@vger.kernel.org, dledford@redhat.com,
maxg@mellanox.com, sergeygo@mellanox.com,
Chuck Lever <chuck.lever@oracle.com>
Subject: Re: [PATCH] IB/iser: Remove support for FMR memory registration
Date: Wed, 13 May 2020 12:49:06 -0700 [thread overview]
Message-ID: <bf17c39b-2e16-6e0b-0a5d-11177cbe3232@acm.org> (raw)
In-Reply-To: <20200513184349.GA4814@unreal>
On 2020-05-13 11:43, Leon Romanovsky wrote:
> mlx4 works too :), I had in mind more older cards than qib, which was
> added to the kernel only ten years ago. For example mlx4 was added 13
> years ago an mthca before git era (>15 years).
Most of the pre-git patches are available in a git repository. This is
the approach I use to view changes that predate the time when Linus
switched to git:
https://stackoverflow.com/questions/3264283/linux-kernel-historical-git-repository-with-full-history
Bart.
next prev parent reply other threads:[~2020-05-13 19:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-12 16:08 [PATCH] IB/iser: Remove support for FMR memory registration Israel Rukshin
2020-05-12 17:16 ` Leon Romanovsky
2020-05-12 17:53 ` Max Gurtovoy
2020-05-12 20:09 ` Bart Van Assche
2020-05-12 20:13 ` Jason Gunthorpe
2020-05-12 20:27 ` Bart Van Assche
2020-05-12 23:06 ` Jason Gunthorpe
2020-05-13 0:53 ` Sagi Grimberg
2020-05-13 7:18 ` Leon Romanovsky
2020-05-13 16:44 ` Dennis Dalessandro
2020-05-13 18:43 ` Leon Romanovsky
2020-05-13 19:49 ` Bart Van Assche [this message]
2020-05-13 8:43 ` Max Gurtovoy
2020-05-13 11:29 ` Tom Talpey
[not found] ` <0C22D41B-89CD-4B2D-B514-8EA06F2233D7@cloudlinux.com>
2020-05-14 10:50 ` Max Gurtovoy
2020-05-14 13:50 ` Tom Talpey
2020-05-17 8:35 ` Sagi Grimberg
2020-05-17 14:55 ` Alexey Lyashkov
2020-05-18 7:16 ` Christoph Hellwig
2020-05-13 0:56 ` Sagi Grimberg
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=bf17c39b-2e16-6e0b-0a5d-11177cbe3232@acm.org \
--to=bvanassche@acm.org \
--cc=chuck.lever@oracle.com \
--cc=dennis.dalessandro@intel.com \
--cc=dledford@redhat.com \
--cc=israelr@mellanox.com \
--cc=jgg@mellanox.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=maxg@mellanox.com \
--cc=sagi@grimberg.me \
--cc=sergeygo@mellanox.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;
as well as URLs for NNTP newsgroup(s).