From: Patrick Venture <venture@google.com>
To: cminyard@mvista.com, thuth@redhat.com, lvivier@redhat.com,
pbonzini@redhat.com, f4bug@amsat.org
Cc: qemu-devel@nongnu.org, Patrick Venture <venture@google.com>
Subject: [PATCH v4 0/2] hw/sensor: Add SB-TSI Temperature Sensor Interface
Date: Mon, 31 Jan 2022 14:29:46 -0800 [thread overview]
Message-ID: <20220131222948.496588-1-venture@google.com> (raw)
v4:
* Added missing signature block from submitter.
v3:
* typofix where I accidentally embedded 'wq' into a string
* moved the type sbtsi definition back into the source file
* renamed the qtest file to use hyphens only
v2:
* Split the commit into a separate patch for the qtest
* Moved the common registers into the new header
* Introduced a new header
Hao Wu (2):
hw/sensor: Add SB-TSI Temperature Sensor Interface
tests: add qtest for hw/sensor/sbtsi
meson.build | 1 +
hw/sensor/trace.h | 1 +
include/hw/sensor/sbtsi.h | 45 +++++
hw/sensor/tmp_sbtsi.c | 369 +++++++++++++++++++++++++++++++++++
tests/qtest/tmp-sbtsi-test.c | 161 +++++++++++++++
hw/sensor/Kconfig | 4 +
hw/sensor/meson.build | 1 +
hw/sensor/trace-events | 5 +
tests/qtest/meson.build | 1 +
9 files changed, 588 insertions(+)
create mode 100644 hw/sensor/trace.h
create mode 100644 include/hw/sensor/sbtsi.h
create mode 100644 hw/sensor/tmp_sbtsi.c
create mode 100644 tests/qtest/tmp-sbtsi-test.c
create mode 100644 hw/sensor/trace-events
--
2.34.1.575.g55b058a8bb-goog
next reply other threads:[~2022-01-31 22:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-31 22:29 Patrick Venture [this message]
2022-01-31 22:29 ` [PATCH v4 1/2] hw/sensor: Add SB-TSI Temperature Sensor Interface Patrick Venture
2023-02-06 23:24 ` Hao Wu
2023-02-07 6:51 ` Philippe Mathieu-Daudé
2023-02-07 9:34 ` Cédric Le Goater
2022-01-31 22:29 ` [PATCH v4 2/2] tests: add qtest for hw/sensor/sbtsi Patrick Venture
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=20220131222948.496588-1-venture@google.com \
--to=venture@google.com \
--cc=cminyard@mvista.com \
--cc=f4bug@amsat.org \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.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 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).