qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fabiano Rosas <farosas@suse.de>
To: qemu-devel@nongnu.org
Cc: qemu-arm@nongnu.org, "Peter Maydell" <peter.maydell@linaro.org>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Thomas Huth" <thuth@redhat.com>
Subject: [PATCH 0/3] arm/Kconfig: Some convenience changes
Date: Tue, 23 May 2023 15:05:22 -0300	[thread overview]
Message-ID: <20230523180525.29994-1-farosas@suse.de> (raw)

Hi,

These are some changes that people asked for/suggested during the
review of previous Kconfig series that I haven't had an opportunity to
prepare until now.

CI run: https://gitlab.com/farosas/qemu/-/pipelines/876384304

Fabiano Rosas (3):
  target/arm: Explain why we need to select ARM_V7M
  arm/Kconfig: Keep Kconfig default entries in default.mak as
    documentation
  arm/Kconfig: Make TCG dependence explicit

 configs/devices/aarch64-softmmu/default.mak |   6 +
 configs/devices/arm-softmmu/default.mak     |  40 +++++++
 hw/arm/Kconfig                              | 123 +++++++++++++-------
 target/arm/Kconfig                          |   3 +
 4 files changed, 131 insertions(+), 41 deletions(-)

-- 
2.35.3



             reply	other threads:[~2023-05-23 18:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-23 18:05 Fabiano Rosas [this message]
2023-05-23 18:05 ` [PATCH 1/3] target/arm: Explain why we need to select ARM_V7M Fabiano Rosas
2023-05-24  6:25   ` Philippe Mathieu-Daudé
2023-05-23 18:05 ` [PATCH 2/3] arm/Kconfig: Keep Kconfig default entries in default.mak as documentation Fabiano Rosas
2023-05-23 18:24   ` Thomas Huth
2023-05-23 18:05 ` [PATCH 3/3] arm/Kconfig: Make TCG dependence explicit Fabiano Rosas
2023-05-23 18:28   ` Thomas Huth
2023-05-24  6:25   ` Philippe Mathieu-Daudé
2023-05-30 12:07 ` [PATCH 0/3] arm/Kconfig: Some convenience changes Peter Maydell

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=20230523180525.29994-1-farosas@suse.de \
    --to=farosas@suse.de \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --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).