From: Johan Hovold <johan@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Alan Stern <stern@rowland.harvard.edu>,
Oliver Neukum <oneukum@suse.com>,
"Paul E . McKenney" <paulmck@linux.vnet.ibm.com>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
Johan Hovold <johan@kernel.org>
Subject: [PATCH 0/2] USB: ldusb: fix ring-buffer locking
Date: Tue, 22 Oct 2019 16:32:01 +0200 [thread overview]
Message-ID: <20191022143203.5260-1-johan@kernel.org> (raw)
Here's a fix for ring-buffer locking issue that was previously posted
as an RFC (1/2), and a new related format specifier clean up.
Johan
Changes since RFC
- drop the head barrier bits which were not needed and update the
commit message (1/2)
- clean up the format specifiers (2/2, new)
Johan Hovold (2):
USB: ldusb: fix ring-buffer locking
USB: ldusb: use unsigned size format specifiers
drivers/usb/misc/ldusb.c | 11 ++++++-----
1 file changed, 6 insertions(+), 5 deletions(-)
--
2.23.0
next reply other threads:[~2019-10-22 14:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-22 14:32 Johan Hovold [this message]
2019-10-22 14:32 ` [PATCH 1/2] USB: ldusb: fix ring-buffer locking Johan Hovold
2019-10-22 14:32 ` [PATCH 2/2] USB: ldusb: use unsigned size format specifiers Johan Hovold
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=20191022143203.5260-1-johan@kernel.org \
--to=johan@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=oneukum@suse.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=stern@rowland.harvard.edu \
/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).