From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jason Gunthorpe Subject: Re: Patches for rdma-core stable-v15 Date: Mon, 13 Nov 2017 12:34:25 -0700 Message-ID: <20171113193425.GO6918@ziepe.ca> References: <6ccc2110-2e27-bacd-b821-f862785a10ca@suse.de> <20171113151437.GL18825@mtr-leonro.local> <20171113163812.GN18825@mtr-leonro.local> <2ee14e55-2998-0dbf-6367-ed6d7915c291@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-rdma-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Devesh Sharma Cc: Nicolas Morey-Chaisemartin , Leon Romanovsky , "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , stable-Xl5UnYtxxKxKUA01WzcqbQ@public.gmane.org List-Id: linux-rdma@vger.kernel.org On Mon, Nov 13, 2017 at 10:56:44PM +0530, Devesh Sharma wrote: > Yeah, > > Jason is asking for further amendments to the barrier mechanism we > have today in rdma-core. That can be handled in a separate patch > series. For now this should be good to go unless Jason suggests > otherwise. It should be fine as is. This is just something we should fix in mainline to ensure we don't get burned by a newer compiler or something. Jason -- 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