From: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Sagi Grimberg <sagi-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org>,
Raju Rangoju <rajur-ut6Up61K2wZBDgjK7y7TUQ@public.gmane.org>
Cc: "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH] RDMA/iser: Fix possible mr leak on device removal event
Date: Fri, 24 Mar 2017 22:31:38 -0400 [thread overview]
Message-ID: <1490409098.2404.41.camel@redhat.com> (raw)
In-Reply-To: <3c42066d-e5b0-fcb8-c434-e5aa2d7c52b9-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org>
On Mon, 2017-03-13 at 10:06 +0200, Sagi Grimberg wrote:
> >
> > Hi Sagi,
>
> Hi Raju,
>
> >
> > Can we expect this patch in next rc ?
>
> I hope so,
>
> Doug, care to get it in the next -rc pull request?
Done.
--
Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
GPG KeyID: B826A3330E572FDD
Key fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD
--
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
prev parent reply other threads:[~2017-03-25 2:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-27 18:16 [PATCH] RDMA/iser: Fix possible mr leak on device removal event Sagi Grimberg
[not found] ` <1488219394-11720-1-git-send-email-sagi-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org>
2017-02-28 13:28 ` Max Gurtovoy
[not found] ` <e2a87fd9-8035-95b3-20de-2389340b9955-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2017-02-28 13:57 ` Raju Rangoju
[not found] ` <CY1PR12MB077458DBD4D7EA18751C40BFBC230@CY1PR12MB0774.namprd12.prod.outlook.com>
[not found] ` <CY1PR12MB077458DBD4D7EA18751C40BFBC230-1s8aH8ViOEdztePUUsNjzQdYzm3356FpvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2017-03-13 8:06 ` Sagi Grimberg
[not found] ` <3c42066d-e5b0-fcb8-c434-e5aa2d7c52b9-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org>
2017-03-25 2:31 ` Doug Ledford [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=1490409098.2404.41.camel@redhat.com \
--to=dledford-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=rajur-ut6Up61K2wZBDgjK7y7TUQ@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.