From: Laurent Vivier <laurent@vivier.eu>
To: qemu-devel@nongnu.org
Cc: Thomas Huth <huth@tuxfamily.org>, Laurent Vivier <laurent@vivier.eu>
Subject: [Qemu-devel] [PULL 4/4] m68k: Remove PCI and USB from config file
Date: Thu, 12 Jan 2017 19:08:21 +0100 [thread overview]
Message-ID: <1484244501-20283-5-git-send-email-laurent@vivier.eu> (raw)
In-Reply-To: <1484244501-20283-1-git-send-email-laurent@vivier.eu>
From: Thomas Huth <huth@tuxfamily.org>
None of the ColdFire boards that we currently support has a PCI or
USB bus (and AFAIK the upcoming q800 machine does not support PCI
and USB either), so we do not need these settings the config file.
Signed-off-by: Thomas Huth <huth@tuxfamily.org>
Message-Id: <20170106083956.53d08923@thl530>
Signed-off-by: Laurent Vivier <laurent@vivier.eu>
---
default-configs/m68k-softmmu.mak | 2 --
1 file changed, 2 deletions(-)
diff --git a/default-configs/m68k-softmmu.mak b/default-configs/m68k-softmmu.mak
index d9552df..60f7cdf 100644
--- a/default-configs/m68k-softmmu.mak
+++ b/default-configs/m68k-softmmu.mak
@@ -1,6 +1,4 @@
# Default configuration for m68k-softmmu
-include pci.mak
-include usb.mak
CONFIG_COLDFIRE=y
CONFIG_PTIMER=y
--
2.7.4
next prev parent reply other threads:[~2017-01-12 18:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-12 18:08 [Qemu-devel] [PULL 0/4] M68k for 2.9 patches Laurent Vivier
2017-01-12 18:08 ` [Qemu-devel] [PULL 1/4] target-m68k: Implement bitfield ops for registers Laurent Vivier
2017-01-12 18:08 ` [Qemu-devel] [PULL 2/4] target-m68k: Implement bitfield ops for memory Laurent Vivier
2017-01-12 18:08 ` [Qemu-devel] [PULL 3/4] target-m68k: Implement bfffo Laurent Vivier
2017-01-12 19:25 ` Richard Henderson
2017-01-12 18:08 ` Laurent Vivier [this message]
2017-01-16 13:21 ` [Qemu-devel] [PULL 0/4] M68k for 2.9 patches 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=1484244501-20283-5-git-send-email-laurent@vivier.eu \
--to=laurent@vivier.eu \
--cc=huth@tuxfamily.org \
--cc=qemu-devel@nongnu.org \
/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).