From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752353AbaAMTNS (ORCPT ); Mon, 13 Jan 2014 14:13:18 -0500 Received: from shards.monkeyblade.net ([149.20.54.216]:37947 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751256AbaAMTNP (ORCPT ); Mon, 13 Jan 2014 14:13:15 -0500 Date: Mon, 13 Jan 2014 11:13:12 -0800 (PST) Message-Id: <20140113.111312.1323236808342705421.davem@davemloft.net> To: pebolle@tiscali.nl Cc: ogerlitz@mellanox.com, jackm@dev.mellanox.co.il, ronye@mellanox.com, hadarh@mellanox.com, netdev@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 0/2] net/mlx4_core: clean up two functions From: David Miller In-Reply-To: <1389099622.15032.18.camel@x41> References: <1389099622.15032.18.camel@x41> X-Mailer: Mew version 6.5 on Emacs 24.1 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Paul Bolle Date: Tue, 07 Jan 2014 14:00:22 +0100 > 0) These two patches are very similar. They both clean up a function to > help GCC understand the codeflow. Both help silence a warning. > > 1) Compile tested only (on 32 bits x86). I do not have this hardware. > > 2) Please note that there's no MAINTAINERS entry for mlx4_core. (Neither > is there an entry for the MLX4 IB driver.) Shouldn't it be added? These patches have been rotting for a week. I know the mlx4 folks said the SRIOV guy inside Mellanox will look at it, but this is taking way too long. This is absolutely unreasonable from Paul's perspective to have to wait this long for a review of these relatively simple patches.