From: Nicholas Piggin <npiggin@gmail.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Nicholas Piggin" <npiggin@gmail.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
qemu-devel@nongnu.org
Subject: [PATCH 0/2] chardev: fixes for recent record/replay on muxed
Date: Wed, 28 Aug 2024 14:33:33 +1000 [thread overview]
Message-ID: <20240828043337.14587-1-npiggin@gmail.com> (raw)
Fix a couple of issues that Peter found with recent record/replay
fix for muxed device.
Thanks,
Nick
Nicholas Piggin (2):
chardev: Fix record/replay error path NULL deref in device creation
chardev: Remove __-prefixed names
chardev/char.c | 22 ++++++++++++----------
1 file changed, 12 insertions(+), 10 deletions(-)
--
2.45.2
next reply other threads:[~2024-08-28 4:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-28 4:33 Nicholas Piggin [this message]
2024-08-28 4:33 ` [PATCH 1/2] chardev: Fix record/replay error path NULL deref in device creation Nicholas Piggin
2024-08-28 15:43 ` Peter Maydell
2024-08-28 4:33 ` [PATCH 2/2] chardev: Remove __-prefixed names Nicholas Piggin
2024-08-28 15:44 ` Peter Maydell
2024-08-28 6:41 ` [PATCH 0/2] chardev: fixes for recent record/replay on muxed Marc-André Lureau
2024-11-27 4:52 ` Nicholas Piggin
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=20240828043337.14587-1-npiggin@gmail.com \
--to=npiggin@gmail.com \
--cc=alex.bennee@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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).