From: Peter Senna Tschudin <peter.senna@gmail.com>
To: jcliburn@gmail.com
Cc: chris.snook@gmail.com, jkosina@suse.cz, rdunlap@infradead.org,
standby24x7@gmail.com, peter.senna@gmail.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: [PATCH 08/19] net: Change variable type to bool
Date: Sun, 22 Sep 2013 00:27:40 +0200 [thread overview]
Message-ID: <1379802471-30252-8-git-send-email-peter.senna@gmail.com> (raw)
In-Reply-To: <1379802471-30252-1-git-send-email-peter.senna@gmail.com>
The variable ret is only assigned the values true and false.
The function atl1c_read_eeprom already returns bool. Change
ret type to bool.
The simplified semantic patch that find this problem is as
follows (http://coccinelle.lip6.fr/):
@exists@
type T;
identifier b;
@@
- T
+ bool
b = ...;
... when any
b = \(true\|false\)
Signed-off-by: Peter Senna Tschudin <peter.senna@gmail.com>
---
drivers/net/ethernet/atheros/atl1c/atl1c_hw.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/ethernet/atheros/atl1c/atl1c_hw.c b/drivers/net/ethernet/atheros/atl1c/atl1c_hw.c
index 3ef7092..1cda49a 100644
--- a/drivers/net/ethernet/atheros/atl1c/atl1c_hw.c
+++ b/drivers/net/ethernet/atheros/atl1c/atl1c_hw.c
@@ -153,7 +153,7 @@ static int atl1c_get_permanent_address(struct atl1c_hw *hw)
bool atl1c_read_eeprom(struct atl1c_hw *hw, u32 offset, u32 *p_value)
{
int i;
- int ret = false;
+ bool ret = false;
u32 otp_ctrl_data;
u32 control;
u32 data;
--
1.8.3.1
next prev parent reply other threads:[~2013-09-21 22:29 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-21 22:27 [PATCH 01/19] arm: Change variable type to bool Peter Senna Tschudin
2013-09-21 22:27 ` [PATCH 02/19] hv: " Peter Senna Tschudin
2013-09-23 12:01 ` Dan Carpenter
2013-09-21 22:27 ` [PATCH 03/19] infiniband: " Peter Senna Tschudin
2013-09-21 22:27 ` [PATCH 04/19] isdn: " Peter Senna Tschudin
2013-09-21 22:27 ` [PATCH 05/19] media: " Peter Senna Tschudin
2013-09-21 22:27 ` [PATCH 06/19] " Peter Senna Tschudin
2013-09-21 22:27 ` [PATCH 07/19] mmc: " Peter Senna Tschudin
2013-09-21 22:27 ` Peter Senna Tschudin [this message]
2013-09-21 22:27 ` [PATCH 09/19] net: " Peter Senna Tschudin
2013-09-23 21:38 ` David Miller
2013-09-21 22:27 ` [PATCH 10/19] " Peter Senna Tschudin
2013-09-21 22:27 ` [PATCH 11/19] wireless: " Peter Senna Tschudin
2013-09-23 19:40 ` Bing Zhao
2013-09-21 22:27 ` [PATCH 12/19] " Peter Senna Tschudin
2013-09-22 8:22 ` Joe Perches
2013-09-24 10:54 ` Kalle Valo
2013-09-21 22:27 ` [PATCH 13/19] rtc: " Peter Senna Tschudin
2013-09-21 22:27 ` [PATCH 14/19] scsi: " Peter Senna Tschudin
2013-09-21 22:27 ` [PATCH 15/19] staging: " Peter Senna Tschudin
2013-09-21 23:15 ` Greg KH
2013-09-21 22:27 ` [PATCH 16/19] " Peter Senna Tschudin
2013-09-21 22:27 ` [PATCH 17/19] " Peter Senna Tschudin
2013-09-22 13:35 ` Pavel Machek
2013-09-21 22:27 ` [PATCH 18/19] nilfs2: " Peter Senna Tschudin
2013-09-21 22:27 ` [PATCH 19/19] net: " Peter Senna Tschudin
[not found] ` <43e0f3a4fb62473e9bdd308a8dc4490f@fmsmsx104.amr.corp.intel.com>
2013-09-23 14:11 ` [PATCH 14/19] scsi: " Dorau, Lukasz
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=1379802471-30252-8-git-send-email-peter.senna@gmail.com \
--to=peter.senna@gmail.com \
--cc=chris.snook@gmail.com \
--cc=jcliburn@gmail.com \
--cc=jkosina@suse.cz \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=standby24x7@gmail.com \
/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).