From mboxrd@z Thu Jan 1 00:00:00 1970 From: Oliver Hartkopp Subject: Re: [patch] can: c_can: precedence error in c_can_chip_config() Date: Mon, 11 Jun 2012 19:42:57 +0200 Message-ID: <4FD62E21.3020209@hartkopp.net> References: <20120609155150.GA6488@elgon.mountain> <4FD4DEF2.6070802@pengutronix.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: Received: from mo-p00-ob.rzone.de ([81.169.146.162]:65338 "EHLO mo-p00-ob.rzone.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750711Ab2FKRm5 (ORCPT ); Mon, 11 Jun 2012 13:42:57 -0400 In-Reply-To: <4FD4DEF2.6070802@pengutronix.de> Sender: linux-can-owner@vger.kernel.org List-ID: To: Marc Kleine-Budde Cc: Dan Carpenter , Wolfgang Grandegger , AnilKumar Ch , "David S. Miller" , Jiri Kosina , linux-can@vger.kernel.org, netdev@vger.kernel.org, kernel-janitors@vger.kernel.org On 10.06.2012 19:52, Marc Kleine-Budde wrote: > On 06/09/2012 05:56 PM, Dan Carpenter wrote: >> (CAN_CTRLMODE_LISTENONLY & CAN_CTRLMODE_LOOPBACK) is (0x02 & 0x01) which >> is zero so the condition is never true. The intent here was to test >> that both flags were set. >> >> Signed-off-by: Dan Carpenter >> --- >> This is a static checker fix. I'm not super familiar with the c_can >> code. > > Good catch. Applied to can-next. > > Marc > Shouldn't this fix go through the net-tree and stable instead of net-next? Regards, Oliver