From: Jamin Lin <jamin_lin@aspeedtech.com>
To: "clg@kaod.org" <clg@kaod.org>,
"jithu.joseph@oss.qualcomm.com" <jithu.joseph@oss.qualcomm.com>,
"open list:All patches CC here" <qemu-devel@nongnu.org>
Cc: Jamin Lin <jamin_lin@aspeedtech.com>,
Troy Lee <troy_lee@aspeedtech.com>,
Kane Chen <kane_chen@aspeedtech.com>,
"nabihestefan@google.com" <nabihestefan@google.com>,
"komlodi@google.com" <komlodi@google.com>
Subject: [PATCH v2 0/4] hw/i3c: Trace fixes and readability improvements from review feedback
Date: Tue, 3 Mar 2026 01:33:23 +0000 [thread overview]
Message-ID: <20260303013322.1297499-1-jamin_lin@aspeedtech.com> (raw)
This small series applies a few follow-up cleanups and bug fixes to the I3C
subsystem based on recent review feedback.
The series is based on the aspeed-next branch from:
https://github.com/legoater/qemu.git
v1:
1. Improve trace correctness/determinism by ensuring num_sent is always
initialized and reported properly.
2. Replace a couple of less readable expressions with clearer helpers/logic,
without changing behavior.
v2:
1. Fix review issue.
Jamin Lin (4):
hw/i3c/dw-i3c: Use ROUND_UP() for RX buffer allocation alignment
hw/i3c/mock-i3c-target: Set num_sent in TX callback to fix trace
reporting
hw/i3c/core: Initialize num_sent in i3c_send_byte()
hw/i3c/mock-i3c-target: Simplify GETMRL byte extraction logic
hw/i3c/core.c | 2 +-
hw/i3c/dw-i3c.c | 2 +-
hw/i3c/mock-i3c-target.c | 11 ++++++++---
3 files changed, 10 insertions(+), 5 deletions(-)
--
2.43.0
next reply other threads:[~2026-03-03 1:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-03 1:33 Jamin Lin [this message]
2026-03-03 1:33 ` [PATCH v2 1/4] hw/i3c/dw-i3c: Use ROUND_UP() for RX buffer allocation alignment Jamin Lin
2026-03-03 1:33 ` [PATCH v2 2/4] hw/i3c/mock-i3c-target: Set num_sent in TX callback to fix trace reporting Jamin Lin
2026-03-03 1:37 ` Jithu Joseph
2026-03-03 1:33 ` [PATCH v2 3/4] hw/i3c/core: Initialize num_sent in i3c_send_byte() Jamin Lin
2026-03-03 1:33 ` [PATCH v2 4/4] hw/i3c/mock-i3c-target: Simplify GETMRL byte extraction logic Jamin Lin
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=20260303013322.1297499-1-jamin_lin@aspeedtech.com \
--to=jamin_lin@aspeedtech.com \
--cc=clg@kaod.org \
--cc=jithu.joseph@oss.qualcomm.com \
--cc=kane_chen@aspeedtech.com \
--cc=komlodi@google.com \
--cc=nabihestefan@google.com \
--cc=qemu-devel@nongnu.org \
--cc=troy_lee@aspeedtech.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.