linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Senna Tschudin <peter.senna@gmail.com>
To: kys@microsoft.com
Cc: haiyangz@microsoft.com, devel@linuxdriverproject.org,
	linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
	Peter Senna Tschudin <peter.senna@gmail.com>
Subject: [PATCH 02/19] hv: Change variable type to bool
Date: Sun, 22 Sep 2013 00:27:34 +0200	[thread overview]
Message-ID: <1379802471-30252-2-git-send-email-peter.senna@gmail.com> (raw)
In-Reply-To: <1379802471-30252-1-git-send-email-peter.senna@gmail.com>

The variable execute_shutdown is only assigned the values true and
false. Change its 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/hv/hv_util.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/hv/hv_util.c b/drivers/hv/hv_util.c
index cb82233..fa37369 100644
--- a/drivers/hv/hv_util.c
+++ b/drivers/hv/hv_util.c
@@ -82,7 +82,7 @@ static void shutdown_onchannelcallback(void *context)
 	struct vmbus_channel *channel = context;
 	u32 recvlen;
 	u64 requestid;
-	u8  execute_shutdown = false;
+	bool  execute_shutdown = false;
 	u8  *shut_txf_buf = util_shutdown.recv_buffer;
 
 	struct shutdown_msg_data *shutdown_msg;
-- 
1.8.3.1


  reply	other threads:[~2013-09-21 22:28 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 ` Peter Senna Tschudin [this message]
2013-09-23 12:01   ` [PATCH 02/19] hv: " 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 ` [PATCH 08/19] net: " Peter Senna Tschudin
2013-09-21 22:27 ` [PATCH 09/19] " 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-2-git-send-email-peter.senna@gmail.com \
    --to=peter.senna@gmail.com \
    --cc=devel@linuxdriverproject.org \
    --cc=haiyangz@microsoft.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=kys@microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    /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).