From: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
To: qemu-devel@nongnu.org
Cc: "Yoshinori Sato" <ysato@users.sourceforge.jp>,
qemu-trivial@nongnu.org,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Michael Walle" <michael@walle.cc>,
"Max Reitz" <mreitz@redhat.com>
Subject: [PATCH 0/4] hw/{lm32,sh4}: Kconfig cleanups
Date: Mon, 8 Feb 2021 14:50:44 +0100 [thread overview]
Message-ID: <20210208135048.2601693-1-f4bug@amsat.org> (raw)
Patches extracted from "target: Provide target-specific Kconfig":
https://www.mail-archive.com/qemu-block@nongnu.org/msg79924.html
Single change, renamed PERIPHERALS as DEVICES as suggested by
Zoltan.
Since LM32/SH4 are not very active, can it go via qemu-trivial@?
Thanks,
Phil.
Philippe Mathieu-Daudé (4):
hw/sh4/Kconfig: Rename CONFIG_SH4 -> CONFIG_SH4_DEVICES
hw/lm32/Kconfig: Introduce CONFIG_LM32_EVR for lm32-evr/uclinux boards
hw/lm32/Kconfig: Rename CONFIG_LM32 -> CONFIG_LM32_DEVICES
hw/lm32/Kconfig: Have MILKYMIST select LM32_DEVICES
default-configs/devices/lm32-softmmu.mak | 2 +-
hw/block/meson.build | 2 +-
hw/char/meson.build | 6 +++---
hw/intc/meson.build | 4 ++--
hw/lm32/Kconfig | 10 +++++++---
hw/lm32/meson.build | 2 +-
hw/sh4/Kconfig | 6 +++---
hw/timer/meson.build | 4 ++--
8 files changed, 20 insertions(+), 16 deletions(-)
--
2.26.2
next reply other threads:[~2021-02-08 20:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-08 13:50 Philippe Mathieu-Daudé [this message]
2021-02-08 13:50 ` [PATCH 1/4] hw/sh4/Kconfig: Rename CONFIG_SH4 -> CONFIG_SH4_DEVICES Philippe Mathieu-Daudé
2021-02-08 20:22 ` Peter Maydell
2021-02-21 18:07 ` Philippe Mathieu-Daudé
2021-02-21 18:10 ` Philippe Mathieu-Daudé
2021-02-08 13:50 ` [PATCH 2/4] hw/lm32/Kconfig: Introduce CONFIG_LM32_EVR for lm32-evr/uclinux boards Philippe Mathieu-Daudé
2021-02-08 13:50 ` [PATCH 3/4] hw/lm32/Kconfig: Rename CONFIG_LM32 -> CONFIG_LM32_DEVICES Philippe Mathieu-Daudé
2021-02-08 13:50 ` [PATCH 4/4] hw/lm32/Kconfig: Have MILKYMIST select LM32_DEVICES Philippe Mathieu-Daudé
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=20210208135048.2601693-1-f4bug@amsat.org \
--to=f4bug@amsat.org \
--cc=michael@walle.cc \
--cc=mreitz@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=ysato@users.sourceforge.jp \
/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).