From mboxrd@z Thu Jan 1 00:00:00 1970 From: dledford@redhat.com (Doug Ledford) Date: Fri, 18 Aug 2017 10:46:58 -0400 Subject: [PATCH v2 0/3] Allow ib_clients to nullify .add but still get .remove events reliably In-Reply-To: <8927ea7d-c6ba-4f32-4ede-0897e83bcda2@mellanox.com> References: <1498983652-18250-1-git-send-email-sagi@grimberg.me> <8927ea7d-c6ba-4f32-4ede-0897e83bcda2@mellanox.com> Message-ID: <1503067618.2598.7.camel@redhat.com> On Sun, 2017-07-02@12:14 +0300, Max Gurtovoy wrote: > > On 7/2/2017 11:20 AM, Sagi Grimberg wrote: > > Some ULPs are just interested in device removal notification with > > no specific > > association because they work over RDMA_CM so no need for detecting > > appearance > > of the devices. That wasn't the because the corresponding > > ib_client_data > > was never added to the device clients list when the ib_client > > registers, > > Patch 1 fixes it. Patches 2-3 just removes the empty .add callout > > nvme(t)-rdma set. > > > > Changes from v1: > > - reword patch 1 change log title > > - collected review tags > > > > Note that this will create a conflict with jens's for-4.13 which we > > added > > ib_client registration to nvmet-rdma. > > > > Sagi Grimberg (3): > > RDMA/core: make ib_device.add method optional > > nvme-rdma: remove redundant empty device add callout > > nvmet-rdma: remove redundant empty device add callout > > All these patches looks fine to me, > > Reviewed-by: Max Gurtovoy Thanks, series applied. -- Doug Ledford GPG KeyID: B826A3330E572FDD Key fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD From mboxrd@z Thu Jan 1 00:00:00 1970 From: Doug Ledford Subject: Re: [PATCH v2 0/3] Allow ib_clients to nullify .add but still get .remove events reliably Date: Fri, 18 Aug 2017 10:46:58 -0400 Message-ID: <1503067618.2598.7.camel@redhat.com> References: <1498983652-18250-1-git-send-email-sagi@grimberg.me> <8927ea7d-c6ba-4f32-4ede-0897e83bcda2@mellanox.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <8927ea7d-c6ba-4f32-4ede-0897e83bcda2-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org> Sender: linux-rdma-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Max Gurtovoy , Sagi Grimberg , linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org Cc: linux-nvme-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org, Christoph Hellwig List-Id: linux-rdma@vger.kernel.org On Sun, 2017-07-02 at 12:14 +0300, Max Gurtovoy wrote: > > On 7/2/2017 11:20 AM, Sagi Grimberg wrote: > > Some ULPs are just interested in device removal notification with > > no specific > > association because they work over RDMA_CM so no need for detecting > > appearance > > of the devices. That wasn't the because the corresponding > > ib_client_data > > was never added to the device clients list when the ib_client > > registers, > > Patch 1 fixes it. Patches 2-3 just removes the empty .add callout > > nvme(t)-rdma set. > > > > Changes from v1: > > - reword patch 1 change log title > > - collected review tags > > > > Note that this will create a conflict with jens's for-4.13 which we > > added > > ib_client registration to nvmet-rdma. > > > > Sagi Grimberg (3): > > RDMA/core: make ib_device.add method optional > > nvme-rdma: remove redundant empty device add callout > > nvmet-rdma: remove redundant empty device add callout > > All these patches looks fine to me, > > Reviewed-by: Max Gurtovoy Thanks, series applied. -- Doug Ledford 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