Return-path: Received: from mms3.broadcom.com ([216.31.210.19]:4586 "EHLO MMS3.broadcom.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752588Ab2BXKj3 convert rfc822-to-8bit (ORCPT ); Fri, 24 Feb 2012 05:39:29 -0500 Message-ID: <4F4768D0.4030109@broadcom.com> (sfid-20120224_113946_190994_AFCFACFE) Date: Fri, 24 Feb 2012 11:39:12 +0100 From: "Arend van Spriel" MIME-Version: 1.0 To: =?UTF-8?B?UmFmYcWCIE1pxYJlY2tp?= cc: "linux-wireless@vger.kernel.org" , "Saul St. John" , "Hauke Mehrtens" , "Larry Finger" Subject: Re: [RFC] bcma: add support for on-chip OTP memory used for SPROM storage References: <1330033977-5741-1-git-send-email-arend@broadcom.com> In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Sender: linux-wireless-owner@vger.kernel.org List-ID: On 02/24/2012 08:52 AM, Rafał Miłecki wrote: >> + srom_control = bcma_read32(bus->drv_cc.core, >> > + BCMA_CC_SROM_CONTROL); >> > + return !!(srom_control& BCMA_CC_SROM_CONTROL_PRESENT); > Does any compiler complain on returning sth like 0xF as a bool? > The compiler probably will not complain, but the caller could have following: if (bcma_sprom_ext_available(bus) == true) { return; } BUG(); I guess you would see the BUG show up in your log with the function returning 0xF. Gr. AvS