From: Ladislav Michl <ladis@linux-mips.org>
To: linux-usb@vger.kernel.org, linux-serial@vger.kernel.org
Cc: "Felipe Balbi" <balbi@kernel.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Michał Mirosław" <mirq-linux@rere.qmqm.pl>
Subject: [PATCH v2 5/5] usb: gadget: u_serial: Use bool for req_busy
Date: Sat, 13 Jul 2019 23:12:33 +0200 [thread overview]
Message-ID: <20190713211233.GF25753@lenoch> (raw)
In-Reply-To: <20190713210853.GA25753@lenoch>
Let's make code more consistent by using bool for req_busy
as it is done for similar variables in struct gs_port.
Signed-off-by: Ladislav Michl <ladis@linux-mips.org>
---
Changes:
- v2: None
drivers/usb/gadget/function/u_serial.c | 11 +++++------
1 file changed, 5 insertions(+), 6 deletions(-)
diff --git a/drivers/usb/gadget/function/u_serial.c b/drivers/usb/gadget/function/u_serial.c
index 2dd6e1211d4a..1b1359a168e7 100644
--- a/drivers/usb/gadget/function/u_serial.c
+++ b/drivers/usb/gadget/function/u_serial.c
@@ -89,7 +89,7 @@ struct gscons_info {
struct kfifo con_buf;
/* protect the buf and busy flag */
spinlock_t con_lock;
- int req_busy;
+ bool req_busy;
struct usb_request *console_req;
};
@@ -918,7 +918,7 @@ static void gs_complete_out(struct usb_ep *ep, struct usb_request *req)
case 0:
/* normal completion */
spin_lock(&info->con_lock);
- info->req_busy = 0;
+ info->req_busy = false;
spin_unlock(&info->con_lock);
wake_up_process(info->console_thread);
@@ -950,7 +950,6 @@ static int gs_console_connect(int port_num)
return -ENOMEM;
info->console_req->complete = gs_complete_out;
info->port = port;
- info->req_busy = 0;
spin_unlock(&info->con_lock);
pr_vdebug("port[%d] console connect!\n", port_num);
return 0;
@@ -989,13 +988,13 @@ static int gs_console_thread(void *data)
size = len;
req->length = kfifo_out(&info->con_buf, req->buf, size);
- info->req_busy = 1;
+ info->req_busy = true;
spin_unlock_irq(&info->con_lock);
status = usb_ep_queue(ep, req, GFP_ATOMIC);
spin_lock_irq(&info->con_lock);
if (status < 0)
- info->req_busy = 0;
+ info->req_busy = false;
} else {
sched:
spin_unlock_irq(&info->con_lock);
@@ -1019,7 +1018,7 @@ static int gs_console_setup(struct console *co, char *options)
info->port = NULL;
info->console_req = NULL;
- info->req_busy = 0;
+ info->req_busy = false;
status = kfifo_alloc(&info->con_buf, GS_CONSOLE_BUF_SIZE, GFP_KERNEL);
if (status) {
--
2.22.0
next prev parent reply other threads:[~2019-07-13 21:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-13 21:08 [PATCH v2 0/5] usb: gadget: u_serial: Fix and cleanup Ladislav Michl
2019-07-13 21:10 ` [PATCH v2 1/5] usb: gadget: u_serial: Fix console_req complete event race Ladislav Michl
2019-07-13 21:10 ` [PATCH v2 2/5] usb: gadget: u_serial: Remove console specific alloc/free req functions Ladislav Michl
2019-07-13 21:11 ` [PATCH v2 3/5] usb: gadget: u_serial: Fix console_req access race Ladislav Michl
2019-07-13 21:11 ` [PATCH v2 4/5] usb: gadget: u_serial: Fix starving write Ladislav Michl
2019-07-13 21:12 ` Ladislav Michl [this message]
2019-07-14 10:04 ` [PATCH v2 0/5] usb: gadget: u_serial: Fix and cleanup Michał Mirosław
2019-07-14 11:37 ` Michał Mirosław
2019-07-14 13:22 ` Ladislav Michl
2019-07-15 10:40 ` Ladislav Michl
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=20190713211233.GF25753@lenoch \
--to=ladis@linux-mips.org \
--cc=balbi@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mirq-linux@rere.qmqm.pl \
/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).