Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751593Ab2KDGAr (ORCPT ); Sun, 4 Nov 2012 01:00:47 -0500 Received: from shards.monkeyblade.net ([149.20.54.216]:34396 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750897Ab2KDGAp (ORCPT ); Sun, 4 Nov 2012 01:00:45 -0500 Date: Sun, 04 Nov 2012 01:00:43 -0500 (EST) Message-Id: <20121104.010043.1842614952525101679.davem@davemloft.net> To: lee.jones@linaro.org Cc: linux-kernel@vger.kernel.org, shemminger@vyatta.com, bridge@lists.linux-foundation.org, netdev@vger.kernel.org Subject: Re: [PATCH 9/9] Avoid 'statement with no effect' compiler warnings From: David Miller In-Reply-To: <1351980150-24145-10-git-send-email-lee.jones@linaro.org> References: <1351980150-24145-1-git-send-email-lee.jones@linaro.org> <1351980150-24145-10-git-send-email-lee.jones@linaro.org> 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 Content-Length: 990 Lines: 25 From: Lee Jones Date: Sat, 3 Nov 2012 23:02:30 +0100 > Instead of issuing (0) statements when !CONFIG_SYSFS which will cause > 'warning: ', we'll use inline statements instead. This will effectively > do the same thing, but suppress any unnecessary warnings. > > Cc: Stephen Hemminger > Cc: bridge@lists.linux-foundation.org > Cc: netdev@vger.kernel.org > Signed-off-by: Lee Jones Applied, but please use more informative subject lines. You should prefix your subject line after [PATCH ...] with the name of the subsystem you are touching, a ": " then the headline description. So here you would have used "bridge: " and that's what I added when I commited this patch. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/