From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:53502) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VF4Dc-0002bJ-3e for qemu-devel@nongnu.org; Thu, 29 Aug 2013 11:33:14 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VF4DS-0005xA-RB for qemu-devel@nongnu.org; Thu, 29 Aug 2013 11:33:08 -0400 Received: from mx1.redhat.com ([209.132.183.28]:36582) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VF4DS-0005wg-Ip for qemu-devel@nongnu.org; Thu, 29 Aug 2013 11:32:58 -0400 Received: from int-mx01.intmail.prod.int.phx2.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id r7TFWuOH019230 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 29 Aug 2013 11:32:57 -0400 Message-ID: <521F6A3C.5060702@redhat.com> Date: Thu, 29 Aug 2013 17:35:24 +0200 From: Laszlo Ersek MIME-Version: 1.0 References: <521F4E76.2090507@redhat.com> <1377783470-8981-2-git-send-email-lersek@redhat.com> <521F53A6.7070200@redhat.com> <521F581A.50301@redhat.com> <521F607F.70001@redhat.com> In-Reply-To: <521F607F.70001@redhat.com> Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 2/2] add some virtio-scsi trace events List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini Cc: qemu-devel@nongnu.org On 08/29/13 16:53, Paolo Bonzini wrote: >> (c) The way I submitted the series, the events in question are disabled >> in "trace-events". Check out the functions themselves: they are >> protected (ie. even the trace_event_get_state() calls are protected) >> with preprocessing directives. I did it this way because I call them in >> several places, and I wanted to keep the #if's centralized. > > Tracing was supposed to remove the need for #if... :) Tracing was supposed not to be broken under dtrace either I presume? > I'll try to salvage the patch. I won't bother next time. I wouldn't want you to waste your time on "salvaging" the clearly broken patches that I submit. To be clear, I considered this series a favor. I don't need it to be accepted. It's easier for me to write ad-hoc debug printf()s each time. They don't depend on anything, they can print just the right set of info that I need, and they work in any component imaginable. In comparison, the bikeshedding you repeatedly indulge in is unbearable. You keep splitting hairs and rejecting patches just because they are not in your taste; you don't need any other reason. NB I haven't just thrown this over the wall. I spent most of today on this series and tried to cover all my bases, perusing the documentation, testing the series, making an honest effort. The one thing that I *can't* prepare for is your adoration of your own taste. If you attribute such paramount importance to your taste, perhaps next time write the crap yourself that you tend to ask me for. Of course there are times when I can't just ignore you and walk away. Maybe I'll look for different responsibilities if that becomes the norm. Laszlo