From: Kalle Valo <kvalo@codeaurora.org>
To: Joe Perches <joe@perches.com>
Cc: David Miller <davem@davemloft.net>,
Stefano Brivio <stefano.brivio@polimi.it>,
Larry Finger <Larry.Finger@lwfinger.net>,
Brett Rudley <brudley@broadcom.com>,
Arend van Spriel <arend@broadcom.com>,
"Franky (Zhenhui) Lin" <frankyl@broadcom.com>,
Hante Meuleman <meuleman@broadcom.com>,
Johannes Berg <johannes.berg@intel.com>,
Emmanuel Grumbach <emmanuel.grumbach@intel.com>,
Intel Linux Wireless <ilw@linux.intel.com>,
linux-wireless@vger.kernel.org, b43-dev@lists.infradead.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
brcm80211-dev-list <brcm80211-dev-list@broadcom.com>
Subject: Re: [net-next] wireless: Use bool function returns of true/false insteadof 1/0
Date: Tue, 7 Apr 2015 17:11:21 +0000 (UTC) [thread overview]
Message-ID: <20150407171121.2DA00140D3F@smtp.codeaurora.org> (raw)
In-Reply-To: <1427678982.2715.55.camel@perches.com>
> Use bool constants as the return values instead of 1 and 0.
>
> Signed-off-by: Joe Perches <joe@perches.com>
Thanks, applied to wireless-drivers-next.git.
Kalle Valo
next prev parent reply other threads:[~2015-04-07 17:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201503260524.AdqSbov9%fengguang.wu@intel.com>
2015-03-25 21:55 ` [PATCH] cxgb4: fix boolreturn.cocci warnings kbuild test robot
2015-03-25 22:14 ` Joe Perches
2015-03-29 19:16 ` David Miller
2015-03-30 1:25 ` [PATCH net-next] ethernet: Use bool function returns of true/false instead of 1/0 Joe Perches
2015-03-30 1:29 ` [PATCH net-next] wireless: " Joe Perches
2015-03-30 1:46 ` Larry Finger
2015-03-30 1:49 ` Joe Perches
2015-04-07 17:11 ` Kalle Valo [this message]
2015-03-30 20:28 ` [PATCH net-next] ethernet: " Jeff Kirsher
2015-03-31 11:10 ` Michal Simek
2015-03-31 19:49 ` Joe Perches
2015-03-31 18:10 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150407171121.2DA00140D3F@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=Larry.Finger@lwfinger.net \
--cc=arend@broadcom.com \
--cc=b43-dev@lists.infradead.org \
--cc=brcm80211-dev-list@broadcom.com \
--cc=brudley@broadcom.com \
--cc=davem@davemloft.net \
--cc=emmanuel.grumbach@intel.com \
--cc=frankyl@broadcom.com \
--cc=ilw@linux.intel.com \
--cc=joe@perches.com \
--cc=johannes.berg@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=meuleman@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=stefano.brivio@polimi.it \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).