From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Sean Hefty" Subject: RE: Re: [PATCH] osm_subnet.c Date: Mon, 5 Oct 2009 09:20:40 -0700 Message-ID: References: <3F6F638B8D880340AB536D29CD4C1E1912C86E8A8F@orsmsx501.amr.corp.intel.com> <20091004001316.GK17846@me> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20091004001316.GK17846@me> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: ofw-bounces@lists.openfabrics.org Errors-To: ofw-bounces@lists.openfabrics.org To: 'Sasha Khapyorsky' , "Smith, Stan" Cc: ofw@lists.openfabrics.org, linux-rdma List-Id: linux-rdma@vger.kernel.org >> /********************************************************************** >> **********************************************************************/ >> -static long compar_mgids(const void *m1, const void *m2) >> +static intn_t compar_mgids(const void *m1, const void *m2) > >Any disagreement about changing a prototype of this method >(cl_pfn_fmap_cmp_t) in complib to use standard type (long) instead of >"homemade" and less clear one ('intn_t')? > >Sasha > >> { >> return memcmp(m1, m2, sizeof(ib_gid_t)); >> } If the function is simply a wrapper around a single call to memcmp, why keep it at all?