From: Amit Shah <amit.shah@redhat.com>
To: "Andreas Färber" <andreas.faerber@web.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 8/8] Move virtio-serial to Makefile.hw
Date: Fri, 8 Jan 2010 10:31:03 +0530 [thread overview]
Message-ID: <20100108050103.GA8999@amit-x200.redhat.com> (raw)
In-Reply-To: <E182C0DA-7273-412C-B6F9-FEF657A4D0AE@web.de>
On (Fri) Jan 08 2010 [01:41:48], Andreas Färber wrote:
>
> Am 07.01.2010 um 08:31 schrieb Amit Shah:
>
>> There's nothing target-dependent in the virtio-serial code so allow it
>> to be compiled just once for all the targets.
>>
>> Signed-off-by: Amit Shah <amit.shah@redhat.com>
>> ---
>> Makefile.hw | 2 +-
>> Makefile.target | 2 +-
>> 2 files changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/Makefile.hw b/Makefile.hw
>> index bd252f5..b6323fa 100644
>> --- a/Makefile.hw
>> +++ b/Makefile.hw
>> @@ -13,7 +13,7 @@ QEMU_CFLAGS+=-I.. -I$(SRC_PATH)/fpu
>>
>> obj-y =
>> obj-y += loader.o
>> -obj-y += virtio.o
>> +obj-y += virtio.o virtio-serial.o
>> obj-y += fw_cfg.o
>> obj-y += watchdog.o
>> obj-$(CONFIG_ECC) += ecc.o
>
> Needs to be rebased and applied against Makefile.objs now, s/obj-y/hw-
> obj-y/.
OK, thanks for the hint. I've rebased my local branch against master.
Amit
next prev parent reply other threads:[~2010-01-08 5:02 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-07 7:31 [Qemu-devel] [PATCH 0/8] virtio-console: Move to qdev, multiple devices, generic ports Amit Shah
2010-01-07 7:31 ` [Qemu-devel] [PATCH 1/8] virtio: Remove duplicate macro definition for max. virtqueues, bump up the max Amit Shah
2010-01-07 7:31 ` [Qemu-devel] [PATCH 2/8] virtio-console: qdev conversion, new virtio-serial-bus Amit Shah
2010-01-07 7:31 ` [Qemu-devel] [PATCH 3/8] virtio-serial-bus: Maintain guest and host port open/close state Amit Shah
2010-01-07 7:31 ` [Qemu-devel] [PATCH 4/8] virtio-serial-bus: Add a port 'name' property for port discovery in guests Amit Shah
2010-01-07 7:31 ` [Qemu-devel] [PATCH 5/8] virtio-serial-bus: Add support for buffering guest output, throttling guests Amit Shah
2010-01-07 7:31 ` [Qemu-devel] [PATCH 6/8] virtio-serial-bus: Add ability to hot-unplug ports Amit Shah
2010-01-07 7:31 ` [Qemu-devel] [PATCH 7/8] virtio-serial: Add a 'virtserialport' device for generic serial port support Amit Shah
2010-01-07 7:31 ` [Qemu-devel] [PATCH 8/8] Move virtio-serial to Makefile.hw Amit Shah
2010-01-08 0:41 ` Andreas Färber
2010-01-08 5:01 ` Amit Shah [this message]
2010-01-08 1:12 ` [Qemu-devel] [PATCH 5/8] virtio-serial-bus: Add support for buffering guest output, throttling guests Jamie Lokier
2010-01-08 5:03 ` Amit Shah
2010-01-08 13:35 ` Jamie Lokier
2010-01-08 16:26 ` Anthony Liguori
2010-01-11 8:39 ` Amit Shah
2010-01-12 0:28 ` Anthony Liguori
2010-01-12 7:08 ` Amit Shah
2010-01-11 8:34 ` Amit Shah
2010-01-11 10:45 ` Jamie Lokier
2010-01-11 11:04 ` Amit Shah
2010-01-11 23:33 ` Jamie Lokier
2010-01-12 0:27 ` Anthony Liguori
2010-01-12 7:16 ` Amit Shah
2010-01-12 15:00 ` Anthony Liguori
2010-01-12 15:13 ` Amit Shah
2010-01-12 15:46 ` Anthony Liguori
2010-01-12 15:49 ` Amit Shah
2010-01-12 15:55 ` Anthony Liguori
2010-01-12 16:04 ` Amit Shah
2010-01-13 17:14 ` Markus Armbruster
2010-01-13 18:31 ` Anthony Liguori
2010-01-11 19:57 ` [Qemu-devel] [PATCH 1/8] virtio: Remove duplicate macro definition for max. virtqueues, bump up the max Anthony Liguori
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=20100108050103.GA8999@amit-x200.redhat.com \
--to=amit.shah@redhat.com \
--cc=andreas.faerber@web.de \
--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).