qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Aleksandar Rikalo" <arikalo@wavecomp.com>,
	"Thomas Huth" <thuth@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>,
	"Aurelien Jarno" <aurelien@aurel32.net>,
	"Aleksandar Markovic" <amarkovic@wavecomp.com>
Subject: [Qemu-devel] [PATCH v4 0/4] Kconfig dependencies for some MIPS machines
Date: Mon,  1 Jul 2019 13:26:08 +0200	[thread overview]
Message-ID: <20190701112612.14758-1-philmd@redhat.com> (raw)

Express the MIPS machine dependencies with Kconfig.

Various issues prevent to use Kconfig with the Boston and Malta
boards. They will be switched later.

v4:
- dropped Boston (Aleksandar required the ITU to be selectable)
- comment why use 'imply' in Jazz (Thomas)

v3:
- addressed review comments from Thomas and Aleksandar
  (noted in each patch)

v2: https://lists.gnu.org/archive/html/qemu-devel/2019-02/msg00887.html
- Do not remove machines from the default config (Thomas)
- Corrected comment about CONFIG_PCI_BONITO (Thomas)

v1: https://www.mail-archive.com/qemu-devel@nongnu.org/msg593013.html

$ git backport-diff -u kconfig_mips-v3
Key:
[----] : patches are identical
[####] : number of functional differences between upstream/downstream patch
The flags [FC] indicate (F)unctional and (C)ontextual differences, respectively

001/4:[down] 'hw/mips: Explicit the semi-hosting feature is always required'
002/4:[----] [--] 'hw/mips: Express dependencies of the MIPSsim machine with Kconfig'
003/4:[----] [-C] 'hw/mips: Express dependencies of the Jazz machine with Kconfig'
004/4:[0005] [FC] 'hw/mips: Express dependencies of the r4k platform with Kconfig'

Regards,

Phil.

Philippe Mathieu-Daudé (4):
  hw/mips: Explicit the semi-hosting feature is always required
  hw/mips: Express dependencies of the MIPSsim machine with Kconfig
  hw/mips: Express dependencies of the Jazz machine with Kconfig
  hw/mips: Express dependencies of the r4k platform with Kconfig

 default-configs/mips-softmmu-common.mak |  7 +++---
 default-configs/mips64-softmmu.mak      |  5 -----
 default-configs/mips64el-softmmu.mak    |  5 -----
 hw/mips/Kconfig                         | 30 +++++++++++++++++++++++++
 4 files changed, 33 insertions(+), 14 deletions(-)

-- 
2.20.1



             reply	other threads:[~2019-07-01 11:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-01 11:26 Philippe Mathieu-Daudé [this message]
2019-07-01 11:26 ` [Qemu-devel] [PATCH v4 1/4] hw/mips: Explicit the semi-hosting feature is always required Philippe Mathieu-Daudé
2019-07-01 12:26   ` Aleksandar Markovic
2019-07-01 11:26 ` [Qemu-devel] [PATCH v4 2/4] hw/mips: Express dependencies of the MIPSsim machine with Kconfig Philippe Mathieu-Daudé
2019-07-01 11:26 ` [Qemu-devel] [PATCH v4 3/4] hw/mips: Express dependencies of the Jazz " Philippe Mathieu-Daudé
2019-07-01 11:26 ` [Qemu-devel] [PATCH v4 4/4] hw/mips: Express dependencies of the r4k platform " Philippe Mathieu-Daudé
2019-07-01 12:24   ` Aleksandar Markovic
2019-07-01 17:11 ` [Qemu-devel] [PATCH v4 0/4] Kconfig dependencies for some MIPS machines Aleksandar Markovic

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=20190701112612.14758-1-philmd@redhat.com \
    --to=philmd@redhat.com \
    --cc=amarkovic@wavecomp.com \
    --cc=arikalo@wavecomp.com \
    --cc=aurelien@aurel32.net \
    --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).