From: John Youn <John.Youn@synopsys.com>
To: "Gustavo A. R. Silva" <gustavo@embeddedor.com>,
John Youn <John.Youn@synopsys.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
balbi@kernel.org
Cc: "linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Gustavo A. R. Silva" <garsilva@embeddedor.com>
Subject: usb: dwc2: gadget: Use true and false for boolean values
Date: Mon, 5 Feb 2018 13:12:49 -0800 [thread overview]
Message-ID: <333168e1-f8b9-87bc-c6ba-a67c9112d686@synopsys.com> (raw)
On 01/23/2018 07:45 AM, Gustavo A. R. Silva wrote:
> Assign true or false to boolean variables instead of an integer value.
>
> This issue was detected with the help of Coccinelle.
>
> Signed-off-by: Gustavo A. R. Silva <gustavo@embeddedor.com>
> ---
> drivers/usb/dwc2/gadget.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/usb/dwc2/gadget.c b/drivers/usb/dwc2/gadget.c
> index e4c3ce0..1f684dd 100644
> --- a/drivers/usb/dwc2/gadget.c
> +++ b/drivers/usb/dwc2/gadget.c
> @@ -116,10 +116,10 @@ static inline void dwc2_gadget_incr_frame_num(struct dwc2_hsotg_ep *hs_ep)
> {
> hs_ep->target_frame += hs_ep->interval;
> if (hs_ep->target_frame > DSTS_SOFFN_LIMIT) {
> - hs_ep->frame_overrun = 1;
> + hs_ep->frame_overrun = true;
> hs_ep->target_frame &= DSTS_SOFFN_LIMIT;
> } else {
> - hs_ep->frame_overrun = 0;
> + hs_ep->frame_overrun = false;
> }
> }
>
>
+Felipe
Acked-by: John Youn <johnyoun@synopsys.com>
Regards,
John
---
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2018-02-05 21:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-05 21:12 John Youn [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-01-23 15:45 usb: dwc2: gadget: Use true and false for boolean values Gustavo A. R. Silva
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=333168e1-f8b9-87bc-c6ba-a67c9112d686@synopsys.com \
--to=john.youn@synopsys.com \
--cc=balbi@kernel.org \
--cc=garsilva@embeddedor.com \
--cc=gregkh@linuxfoundation.org \
--cc=gustavo@embeddedor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@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