From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:53638) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cXqpQ-0002FZ-JZ for qemu-devel@nongnu.org; Sun, 29 Jan 2017 09:51:41 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cXqpN-0002Dz-Dy for qemu-devel@nongnu.org; Sun, 29 Jan 2017 09:51:40 -0500 Received: from roura.ac.upc.es ([147.83.33.10]:33667) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cXqpN-0002DH-15 for qemu-devel@nongnu.org; Sun, 29 Jan 2017 09:51:37 -0500 From: =?utf-8?Q?Llu=C3=ADs_Vilanova?= References: <148434048970.31446.17153056211582691244.stgit@frigg.lan> <148434050231.31446.10929552655201551997.stgit@frigg.lan> <597a44c3-2518-2d24-598c-4867f57dfa7b@twiddle.net> <87d1fp13r4.fsf@ac.upc.edu> Date: Sun, 29 Jan 2017 16:51:26 +0200 In-Reply-To: <87d1fp13r4.fsf@ac.upc.edu> (=?utf-8?Q?=22Llu=C3=ADs?= Vilanova"'s message of "Sun, 15 Jan 2017 03:00:31 +0100") Message-ID: <87vasxnclt.fsf@frigg.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [PATCH v7 2/7] trace: Make trace_get_vcpu_event_count() inlinable List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Richard Henderson Cc: qemu-devel@nongnu.org, Eduardo Habkost , Stefan Hajnoczi Llu=C3=ADs Vilanova writes: > Richard Henderson writes: >> On 01/13/2017 12:48 PM, Llu=C3=ADs Vilanova wrote: >>> @@ -237,7 +237,7 @@ char *trace_opt_parse(const char *optarg); >>> * >>> * Return the number of known vcpu-specific events >>> */ >>> -uint32_t trace_get_vcpu_event_count(void); >>> +static uint32_t trace_get_vcpu_event_count(void); >>>=20 >> Why is this declaration still here? It's redundant with the inline. > I can remove it if you feel strongly against it, but I kept it to maintain > consistency with the rest of the file. As I said in the previous series, = this is > the style used in the header. All "public" functions (inlined or not) are > declared there with their documentation. > Being inlined is an implementation detail (inlines are defined on a separ= ate > header), but given C's design it leaks through the static declaration. Ping. Cheers, Lluis