From: Bart Van Assche <bart.vanassche-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org>
To: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>,
Sagi Grimberg <sagi-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org>,
Laurence Oberman
<loberman-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
"leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org"
<leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
"linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: [PATCH v2 0/7] IB/srp: Second series of patches for kernel v4.7
Date: Thu, 12 May 2016 10:46:41 -0700 [thread overview]
Message-ID: <5734C181.2020003@sandisk.com> (raw)
Hello Doug,
Since the first eight patches of the patch series "[PATCH 0/11] More SRP
patches for kernel v4.7" have already been applied I'm reposting version
two of the reworked remaining patches. These patches are:
0001-IB-srp-Print-ib_srp-prefix-once.patch
0002-IB-srp-Fix-a-memory-descriptor-leak-in-an-error-path.patch
0003-IB-srp-Fix-srp_create_target-error-handling.patch
0004-IB-core-Enhance-ib_map_mr_sg.patch
0005-IB-srp-Swap-two-code-blocks-in-srp_add_one.patch
0006-IB-srp-Prevent-mapping-failures.patch
0007-IB-srp-Do-not-register-memory-if-never_register-has-.patch
The changes compared to v1 of this patch series are:
* Fixed a bug in patch 4/7, the patch that modifies ib_map_mr_sg().
* Added code that checks how many data has been mapped in patch 6/7.
This code can be enabled and disabled dynamically via the dynamic
debug mechanism.
* Added a seventh patch that introduces the never_register parameter.
This patch series is based on Christoph's RDMA read/write API rework
patch series.
A git tree with these patches is available at
https://github.com/bvanassche/linux/commits/srp-initiator-for-next.
Thanks,
Bart.
--
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
next reply other threads:[~2016-05-12 17:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-12 17:46 Bart Van Assche [this message]
[not found] ` <5734C181.2020003-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org>
2016-05-12 17:47 ` [PATCH 1/7] IB/srp: Print "ib_srp: " prefix once Bart Van Assche
2016-05-12 17:48 ` [PATCH 2/7] IB/srp: Fix a memory descriptor leak in an error path Bart Van Assche
2016-05-12 17:48 ` [PATCH 3/7] IB/srp: Fix srp_create_target() error handling Bart Van Assche
2016-05-12 17:49 ` [PATCH 4/7] IB/core: Enhance ib_map_mr_sg() Bart Van Assche
2016-05-12 17:49 ` [PATCH 5/7] IB/srp: Swap two code blocks in srp_add_one() Bart Van Assche
2016-05-12 17:50 ` [PATCH 6/7] IB/srp: Prevent mapping failures Bart Van Assche
2016-05-12 17:51 ` [PATCH 7/7] IB/srp: Do not register memory if never_register has been set Bart Van Assche
2016-05-12 18:44 ` [PATCH v2 0/7] IB/srp: Second series of patches for kernel v4.7 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=5734C181.2020003@sandisk.com \
--to=bart.vanassche-xdaiopvojttbdgjk7y7tuq@public.gmane.org \
--cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=hch-jcswGhMUV9g@public.gmane.org \
--cc=leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=loberman-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=sagi-NQWnxTmZq1alnMjI0IkVqw@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).