From: Jan Kiszka <jan.kiszka@siemens.com>
To: Avi Kivity <avi@redhat.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>, kvm-devel <kvm@vger.kernel.org>
Subject: Re: [PATCH] qemu-kvm: Cleanup compatfd makefile rule
Date: Mon, 21 Sep 2009 12:25:05 +0200 [thread overview]
Message-ID: <4AB75481.9010603@siemens.com> (raw)
In-Reply-To: <4AB74783.406@redhat.com>
Avi Kivity wrote:
> On 09/18/2009 08:31 PM, Jan Kiszka wrote:
>> Signed-off-by: Jan Kiszka<jan.kiszka@siemens.com>
>> ---
>>
>> Makefile | 7 +------
>> 1 files changed, 1 insertions(+), 6 deletions(-)
>>
>> diff --git a/Makefile b/Makefile
>> index 6a9ca7c..6855fa2 100644
>> --- a/Makefile
>> +++ b/Makefile
>> @@ -65,9 +65,8 @@ recurse-all: $(SUBDIR_RULES) $(ROMSUBDIR_RULES)
>>
>> block-obj-y = cutils.o cache-utils.o qemu-malloc.o qemu-option.o module.o
>> block-obj-y += nbd.o block.o aio.o aes.o osdep.o
>> -block-obj-$(CONFIG_POSIX) += posix-aio-compat.o
>> +block-obj-$(CONFIG_POSIX) += posix-aio-compat.o compatfd.o
>> block-obj-$(CONFIG_LINUX_AIO) += linux-aio.o
>> -block-obj-y += compatfd.o
>>
>
> This looks to be already obsolete, but note that I prefer kvm-specific
> changes to be on their own lines to reduce merge conflicts. That is how
> the code look now.
I don't mind if separate line or not, just use the proper CONFIG_POSIX
conditional.
Jan
--
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2009-09-21 10:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-18 17:31 [PATCH] qemu-kvm: Cleanup compatfd makefile rule Jan Kiszka
2009-09-21 9:29 ` Avi Kivity
2009-09-21 10:25 ` Jan Kiszka [this message]
2009-09-21 11:49 ` Avi Kivity
2009-09-21 11:53 ` Jan Kiszka
2009-09-21 11:56 ` Avi Kivity
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=4AB75481.9010603@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.