From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: sparclinux@vger.kernel.org
Cc: "David S. Miller" <davem@davemloft.net>,
Joshua Rogers <linux@joshua.hu>,
Jiri Slaby <jirislaby@kernel.org>,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
stable <stable@kernel.org>
Subject: [PATCH 0/2] tty: vcc: Some small vcc bugfixes found by code scans
Date: Fri, 31 Jul 2026 10:15:16 +0200 [thread overview]
Message-ID: <20260731-aisle-tty-vcc-v1-0-962e18beb8a8@linuxfoundation.org> (raw)
Joshua at AISLE has been kind enough to run a bunch of scans on the
tty/serial code and here are two minor fixes for the vcc code that the
tools found.
One note, is this code even used anymore? Seems to be sparc-specific,
just wanted to know if this platform is still alive? If not, I'll be
glad to delete this file :)
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
---
Joshua Rogers (2):
tty: vcc: zero-initialize control packet in vcc_send_ctl()
tty: vcc: hold port lock when clearing tty pointer in vcc_cleanup
drivers/tty/vcc.c | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
---
base-commit: 8ba098e6b6ff0db8edf28528d1552be261af30d4
change-id: 20260731-aisle-tty-vcc-8ea9ace26f6f
Best regards,
--
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
next reply other threads:[~2026-07-31 8:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 8:15 Greg Kroah-Hartman [this message]
2026-07-31 8:15 ` [PATCH 1/2] tty: vcc: zero-initialize control packet in vcc_send_ctl() Greg Kroah-Hartman
2026-07-31 8:29 ` Jiri Slaby
2026-07-31 8:32 ` Greg Kroah-Hartman
2026-07-31 9:16 ` Jiri Slaby
2026-07-31 12:02 ` Greg Kroah-Hartman
2026-07-31 8:15 ` [PATCH 2/2] tty: vcc: hold port lock when clearing tty pointer in vcc_cleanup Greg Kroah-Hartman
2026-07-31 8:32 ` Jiri Slaby
2026-08-03 14:09 ` Greg Kroah-Hartman
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=20260731-aisle-tty-vcc-v1-0-962e18beb8a8@linuxfoundation.org \
--to=gregkh@linuxfoundation.org \
--cc=davem@davemloft.net \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux@joshua.hu \
--cc=sparclinux@vger.kernel.org \
--cc=stable@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