From mboxrd@z Thu Jan 1 00:00:00 1970 From: jgg@mellanox.com (Jason Gunthorpe) Date: Wed, 30 May 2018 09:30:36 -0600 Subject: [PATCH 01/17] IB/isert: fix T10-pi check mask setting In-Reply-To: <6e9b09a2-6b17-c128-fad1-198db6059a62@mellanox.com> References: <452bfcde-ee3c-a4e5-e2d0-43114099590a@mellanox.com> <20180528120359.GA13368@lst.de> <99191c8c-b03e-f40d-ffd9-a73e01d0ae2a@mellanox.com> <20180528163324.GF17491@mellanox.com> <6c7335c1-1d59-f764-be46-9aab46eb8458@mellanox.com> <20180529192329.GJ18442@mellanox.com> <20180529221943.GR18442@mellanox.com> <6e9b09a2-6b17-c128-fad1-198db6059a62@mellanox.com> Message-ID: <20180530153036.GD30764@mellanox.com> On Wed, May 30, 2018@11:07:17AM +0300, Max Gurtovoy wrote: > > > On 5/30/2018 1:19 AM, Jason Gunthorpe wrote: > >On Tue, May 29, 2018@06:11:18PM -0400, Martin K. Petersen wrote: > >> > >>Jason, > >> > >>>>we must wait until Martin PR for sure... > >>> > >>>Hmm, maybe we should have sent this patch through rdma in that > >>>case.. The merge window is soon anyhow so it doesn't really matter > >>>this time - but you need to think about what tree patches need to go > >>>to when building your patch plan, don't just send a large unstructured > >>>series like this and expect the maintainers to figure out all the > >>>dependencies! > >> > >>I am also happy to just drop the patch from scsi-fixes and you can > >>funnel everything through RDMA. Doesn't matter to me. > > > >Sure, if you can still do that.. Max can you send me all four patches > >tomorrow and I'll route them through rdma. > > Yes sure. I'm sorry for the ping-pong, I've tried to cover this in the cover > letter but I guess I should've mentioned specifically what patches goes > through which tree. Just in general don't send such a jumble of patches for multiple maintainers under one cover letter. It is error prone to sort it out. Jason From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-eopbgr00079.outbound.protection.outlook.com ([40.107.0.79]:57285 "EHLO EUR02-AM5-obe.outbound.protection.outlook.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753041AbeE3Pa7 (ORCPT ); Wed, 30 May 2018 11:30:59 -0400 Date: Wed, 30 May 2018 09:30:36 -0600 From: Jason Gunthorpe To: Max Gurtovoy Cc: "Martin K. Petersen" , Christoph Hellwig , keith.busch@intel.com, linux-nvme@lists.infradead.org, sagi@grimberg.me, leon@kernel.org, oren@mellanox.com, idanb@mellanox.com, vladimirk@mellanox.com, stable@vger.kernel.org Subject: Re: [PATCH 01/17] IB/isert: fix T10-pi check mask setting Message-ID: <20180530153036.GD30764@mellanox.com> References: <452bfcde-ee3c-a4e5-e2d0-43114099590a@mellanox.com> <20180528120359.GA13368@lst.de> <99191c8c-b03e-f40d-ffd9-a73e01d0ae2a@mellanox.com> <20180528163324.GF17491@mellanox.com> <6c7335c1-1d59-f764-be46-9aab46eb8458@mellanox.com> <20180529192329.GJ18442@mellanox.com> <20180529221943.GR18442@mellanox.com> <6e9b09a2-6b17-c128-fad1-198db6059a62@mellanox.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6e9b09a2-6b17-c128-fad1-198db6059a62@mellanox.com> Sender: stable-owner@vger.kernel.org List-ID: On Wed, May 30, 2018 at 11:07:17AM +0300, Max Gurtovoy wrote: > > > On 5/30/2018 1:19 AM, Jason Gunthorpe wrote: > >On Tue, May 29, 2018 at 06:11:18PM -0400, Martin K. Petersen wrote: > >> > >>Jason, > >> > >>>>we must wait until Martin PR for sure... > >>> > >>>Hmm, maybe we should have sent this patch through rdma in that > >>>case.. The merge window is soon anyhow so it doesn't really matter > >>>this time - but you need to think about what tree patches need to go > >>>to when building your patch plan, don't just send a large unstructured > >>>series like this and expect the maintainers to figure out all the > >>>dependencies! > >> > >>I am also happy to just drop the patch from scsi-fixes and you can > >>funnel everything through RDMA. Doesn't matter to me. > > > >Sure, if you can still do that.. Max can you send me all four patches > >tomorrow and I'll route them through rdma. > > Yes sure. I'm sorry for the ping-pong, I've tried to cover this in the cover > letter but I guess I should've mentioned specifically what patches goes > through which tree. Just in general don't send such a jumble of patches for multiple maintainers under one cover letter. It is error prone to sort it out. Jason