From: Wei Huang <wei@redhat.com>
To: qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, peter.maydell@linaro.org,
imammedo@redhat.com, shannon.zhao@linaro.org,
zhaoshenglong@huawei.com
Subject: [Qemu-trivial] [PATCH 2/2] ARM: PL061: Misc cleaning fields for PL061 device state
Date: Mon, 1 Feb 2016 12:20:06 -0500 [thread overview]
Message-ID: <1454347206-23717-2-git-send-email-wei@redhat.com> (raw)
In-Reply-To: <1454347206-23717-1-git-send-email-wei@redhat.com>
This patch removes float_high field of PL061State, which doesn't seem
to be used anywhere.
Signed-off-by: Wei Huang <wei@redhat.com>
---
hw/gpio/pl061.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/hw/gpio/pl061.c b/hw/gpio/pl061.c
index 342a70d..2c08e88 100644
--- a/hw/gpio/pl061.c
+++ b/hw/gpio/pl061.c
@@ -56,7 +56,6 @@ typedef struct PL061State {
uint32_t slr;
uint32_t den;
uint32_t cr;
- uint32_t float_high;
uint32_t amsel;
qemu_irq irq;
qemu_irq out[8];
@@ -88,7 +87,6 @@ static const VMStateDescription vmstate_pl061 = {
VMSTATE_UINT32(slr, PL061State),
VMSTATE_UINT32(den, PL061State),
VMSTATE_UINT32(cr, PL061State),
- VMSTATE_UINT32(float_high, PL061State),
VMSTATE_UINT32_V(amsel, PL061State, 2),
VMSTATE_END_OF_LIST()
}
--
1.8.3.1
WARNING: multiple messages have this Message-ID (diff)
From: Wei Huang <wei@redhat.com>
To: qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, peter.maydell@linaro.org,
imammedo@redhat.com, shannon.zhao@linaro.org,
zhaoshenglong@huawei.com
Subject: [Qemu-devel] [PATCH 2/2] ARM: PL061: Misc cleaning fields for PL061 device state
Date: Mon, 1 Feb 2016 12:20:06 -0500 [thread overview]
Message-ID: <1454347206-23717-2-git-send-email-wei@redhat.com> (raw)
In-Reply-To: <1454347206-23717-1-git-send-email-wei@redhat.com>
This patch removes float_high field of PL061State, which doesn't seem
to be used anywhere.
Signed-off-by: Wei Huang <wei@redhat.com>
---
hw/gpio/pl061.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/hw/gpio/pl061.c b/hw/gpio/pl061.c
index 342a70d..2c08e88 100644
--- a/hw/gpio/pl061.c
+++ b/hw/gpio/pl061.c
@@ -56,7 +56,6 @@ typedef struct PL061State {
uint32_t slr;
uint32_t den;
uint32_t cr;
- uint32_t float_high;
uint32_t amsel;
qemu_irq irq;
qemu_irq out[8];
@@ -88,7 +87,6 @@ static const VMStateDescription vmstate_pl061 = {
VMSTATE_UINT32(slr, PL061State),
VMSTATE_UINT32(den, PL061State),
VMSTATE_UINT32(cr, PL061State),
- VMSTATE_UINT32(float_high, PL061State),
VMSTATE_UINT32_V(amsel, PL061State, 2),
VMSTATE_END_OF_LIST()
}
--
1.8.3.1
next prev parent reply other threads:[~2016-02-01 17:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-01 17:20 [Qemu-trivial] [PATCH 1/2] ARM: PL061: Clear PL061 device state after reset Wei Huang
2016-02-01 17:20 ` [Qemu-devel] " Wei Huang
2016-02-01 17:20 ` Wei Huang [this message]
2016-02-01 17:20 ` [Qemu-devel] [PATCH 2/2] ARM: PL061: Misc cleaning fields for PL061 device state Wei Huang
2016-02-01 18:01 ` [Qemu-trivial] " Peter Maydell
2016-02-01 18:01 ` [Qemu-devel] " Peter Maydell
2016-02-02 7:03 ` [Qemu-trivial] " Michael Tokarev
2016-02-02 7:03 ` [Qemu-devel] " Michael Tokarev
2016-02-02 15:16 ` [Qemu-trivial] " Wei Huang
2016-02-02 15:16 ` [Qemu-devel] " Wei Huang
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=1454347206-23717-2-git-send-email-wei@redhat.com \
--to=wei@redhat.com \
--cc=imammedo@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=shannon.zhao@linaro.org \
--cc=zhaoshenglong@huawei.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.