Return-Path: Received: from mail-wi0-f175.google.com ([209.85.212.175]:34219 "EHLO mail-wi0-f175.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751420AbbDHINw (ORCPT ); Wed, 8 Apr 2015 04:13:52 -0400 Received: by widjs5 with SMTP id js5so27300453wid.1 for ; Wed, 08 Apr 2015 01:13:50 -0700 (PDT) Message-ID: <5524E33B.5050403@profitbricks.com> Date: Wed, 08 Apr 2015 10:13:47 +0200 From: Michael Wang MIME-Version: 1.0 To: Jason Gunthorpe CC: Roland Dreier , Sean Hefty , linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org, netdev@vger.kernel.org, Hal Rosenstock , Tom Tucker , Steve Wise , Hoang-Nam Nguyen , Christoph Raisch , Mike Marciniszyn , Eli Cohen , Faisal Latif , Upinder Malhi , Trond Myklebust , "J. Bruce Fields" , "David S. Miller" , Ira Weiny , PJ Waskiewicz , Tatyana Nikolova , Or Gerlitz , Jack Morgenstein , Haggai Eran , Ilya Nelkenbaum , Yann Droneaud , Bart Van Assche , Shachar Raindel , Sagi Grimberg , Devesh Sharma , Matan Barak , Moni Shoua , Jiri Kosina , Selvin Xavier , Mitesh Ahuja , Li RongQing , Rasmus Villemoes , Alex Estrin , Doug Ledford , Eric Dumazet , Erez Shitrit , Tom Gundersen , Chuck Lever Subject: Re: [PATCH v2 03/17] IB/Verbs: Use management helper cap_ib_mad() for mad-check References: <5523CCD5.6030401@profitbricks.com> <5523CDDE.4050209@profitbricks.com> <20150407172612.GA15704@obsidianresearch.com> In-Reply-To: <20150407172612.GA15704@obsidianresearch.com> Content-Type: text/plain; charset=windows-1252 Sender: linux-nfs-owner@vger.kernel.org List-ID: On 04/07/2015 07:26 PM, Jason Gunthorpe wrote: > On Tue, Apr 07, 2015 at 02:30:22PM +0200, Michael Wang wrote: > >> - if (rdma_node_get_transport(device->node_type) != RDMA_TRANSPORT_IB) >> - return; >> - >> if (device->node_type == RDMA_NODE_IB_SWITCH) { >> start = 0; >> end = 0; >> @@ -3069,6 +3066,9 @@ static void ib_mad_init_device(struct ib_device *device) >> } >> >> for (i = start; i <= end; i++) { >> + if (!cap_ib_mad(device, i)) >> + continue; >> + > > I would prefer to see these changes in control flow as dedicated > patches, at the top of your patch stack. > > For this kind of work a patch should be mechanical changes only, it is > easier to review that way. > > Same comment applies throughout. Make sense :-) I will re-organize the sequence and put them at last. Regards, Michael Wang > > Jason >