From: "Andreas Färber" <afaerber@suse.de>
To: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Cc: Igor Mammedov <imammedo@redhat.com>,
Eduardo Habkost <ehabkost@redhat.com>
Subject: Re: [Qemu-devel] [PULL 16/16] target-i386: Move KVM default-vendor hack to instance_init
Date: Sun, 09 Feb 2014 02:41:47 +0100 [thread overview]
Message-ID: <52F6DCDB.3050903@suse.de> (raw)
In-Reply-To: <52F6BEB1.2090606@redhat.com>
Am 09.02.2014 00:33, schrieb Paolo Bonzini:
> If you consider it a style bug, post a patch to add the
> -Wdeclaration-after-statement flag and/or to detect in checkpatch.pl.
> Until then, things are left to everyone's taste. AFAIU declarations
> after statements are discouraged but not prohibited.
Huh? Where is the justice in people telling me not to do things and to
change my patches in certain ways and now Igor, Eduardo, you and others
taking different measures for yourselves? Either rules apply equally to
all, or they apply to none of us!
I have been fair to ping you for my CPUState series in the past until
you either provided Acked-bys or gave me a go-ahead for KVM parts; you
are not returning that courtesy now and are trying to justify that.
I further usually gave a clear last-call before including in a pull.
If you read MAINTAINERS, you will find that target-i386/cpu.c is part of
the CPU subsystem under my maintenance, so I expect that patches
touching it wait for an okay before they get applied through some tree.
If you want to take over that file, just ask nicely and we can come to
terms - at the time no one else had volunteered.
Similarly I feel that you have given quite some destructive feedback to
my favorite series the last few months, not clearly stating how you want
things done instead. If you're jealous that you didn't make top 1 at KVM
Forum 2013 then you have lots of chances to catch up for 2.0
(virtio-scsi qtests, QOM realize conversions, another go at recursive
realization, creating proper devices from legacy code, ... just to give
some ideas) rather than being unfriendly to me and obstructive to my
line of work. I don't personally consider such statistics telling. And
I'm not aware of anything I've broken in KVM or SCSI that might explain.
Regards,
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2014-02-09 1:42 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-03 16:38 [Qemu-devel] [PULL 00/16] KVM changes for 2014-02-03 Paolo Bonzini
2014-02-03 16:38 ` [Qemu-devel] [PULL 01/16] target-i386: kvm_cpu_fill_host(): Kill unused code Paolo Bonzini
2014-02-03 16:38 ` [Qemu-devel] [PULL 02/16] target-i386: kvm_cpu_fill_host(): No need to check level Paolo Bonzini
2014-02-03 16:38 ` [Qemu-devel] [PULL 03/16] target-i386: kvm_cpu_fill_host(): No need to check CPU vendor Paolo Bonzini
2014-02-03 16:38 ` [Qemu-devel] [PULL 04/16] target-i386: kvm_cpu_fill_host(): No need to check xlevel2 Paolo Bonzini
2014-02-03 16:39 ` [Qemu-devel] [PULL 05/16] target-i386: kvm_cpu_fill_host(): Set all feature words at end of function Paolo Bonzini
2014-02-03 16:39 ` [Qemu-devel] [PULL 06/16] target-i386: kvm_cpu_fill_host(): Fill feature words in a loop Paolo Bonzini
2014-02-03 16:39 ` [Qemu-devel] [PULL 07/16] target-i386: kvm_check_features_against_host(): Kill feature word array Paolo Bonzini
2014-02-03 16:39 ` [Qemu-devel] [PULL 08/16] kvm: print suberror on all internal errors Paolo Bonzini
2014-02-03 16:39 ` [Qemu-devel] [PULL 09/16] KVM: fix coexistence of KVM and Hyper-V leaves Paolo Bonzini
2014-02-03 16:39 ` [Qemu-devel] [PULL 10/16] kvm: make availability of Hyper-V enlightenments dependent on KVM_CAP_HYPERV Paolo Bonzini
2014-02-03 16:39 ` [Qemu-devel] [PULL 11/16] kvm: make hyperv hypercall and guest os id MSRs migratable Paolo Bonzini
2014-02-03 16:39 ` [Qemu-devel] [PULL 12/16] kvm: make hyperv vapic assist page migratable Paolo Bonzini
2014-02-03 16:39 ` [Qemu-devel] [PULL 13/16] kvm: add support for hyper-v timers Paolo Bonzini
2014-03-04 15:14 ` Peter Maydell
2014-02-03 16:39 ` [Qemu-devel] [PULL 14/16] target-i386: Eliminate CONFIG_KVM #ifdefs Paolo Bonzini
2014-02-03 16:39 ` [Qemu-devel] [PULL 15/16] target-i386: Don't change x86_def_t struct on cpu_x86_register() Paolo Bonzini
2014-02-03 16:39 ` [Qemu-devel] [PULL 16/16] target-i386: Move KVM default-vendor hack to instance_init Paolo Bonzini
2014-02-08 17:28 ` Andreas Färber
2014-02-08 23:33 ` Paolo Bonzini
2014-02-09 0:10 ` Peter Maydell
2014-02-09 0:23 ` Peter Maydell
2014-02-09 6:57 ` Paolo Bonzini
2014-02-09 8:25 ` [Qemu-devel] [PATCH] target-i386: Don't declare variables in the middle of blocks Eduardo Habkost
2014-02-19 19:39 ` [Qemu-devel] [qom-cpu PATCH v2] " Eduardo Habkost
2014-02-20 12:48 ` Andreas Färber
2014-02-09 8:06 ` [Qemu-devel] [PULL 16/16] target-i386: Move KVM default-vendor hack to instance_init Eduardo Habkost
2014-02-09 10:13 ` Andreas Färber
2014-02-09 13:06 ` Peter Maydell
2014-02-09 1:41 ` Andreas Färber [this message]
2014-02-09 6:52 ` Paolo Bonzini
2014-02-06 11:12 ` [Qemu-devel] [PULL 00/16] KVM changes for 2014-02-03 Peter Maydell
2014-02-06 23:41 ` Paolo Bonzini
2014-02-07 0:03 ` 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=52F6DCDB.3050903@suse.de \
--to=afaerber@suse.de \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=pbonzini@redhat.com \
--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).