From: Rakesh Jeyasingh <rakeshjb010@gmail.com>
To: qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, rakeshjb010@gmail.com
Subject: [PATCH 0/2] pl011: Refactor DR register handling in Rust implementation
Date: Mon, 7 Apr 2025 23:43:25 +0530 [thread overview]
Message-ID: <20250407181327.171563-1-rakeshjb010@gmail.com> (raw)
This patch series refactors the rust PL011Registers read/write for DR:
Patch 1/2 extracts DR read logic
Patch 2/2 extracts DR write logic
Rakesh Jeyasingh (2):
rust/hw/char/pl011: Extract extract DR read logic into separate
function
rust/hw/char/pl011: Extract DR write logic into separate function
rust/hw/char/pl011/src/device.rs | 53 +++++++++++++++++---------------
1 file changed, 28 insertions(+), 25 deletions(-)
--
2.43.0
next reply other threads:[~2025-04-07 18:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-07 18:13 Rakesh Jeyasingh [this message]
2025-04-07 18:13 ` [PATCH 1/2] rust/hw/char/pl011: Extract extract DR read logic into separate function Rakesh Jeyasingh
2025-04-07 18:13 ` [PATCH 2/2] rust/hw/char/pl011: Extract DR write " Rakesh Jeyasingh
2025-04-15 11:12 ` [PATCH 0/2] pl011: Refactor DR register handling in Rust implementation Paolo Bonzini
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=20250407181327.171563-1-rakeshjb010@gmail.com \
--to=rakeshjb010@gmail.com \
--cc=pbonzini@redhat.com \
--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).