[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AA4613D1-106B-4B4D-9470-EBEA2A527DC7@gmail.com>
Date: Mon, 11 May 2020 15:48:55 -0300
From: Arnaldo Melo <arnaldo.melo@...il.com>
To: "Gustavo A. R. Silva" <gustavoars@...nel.org>
CC: Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...hat.com>,
Mark Rutland <mark.rutland@....com>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Jiri Olsa <jolsa@...hat.com>,
Namhyung Kim <namhyung@...nel.org>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] perf script: Replace zero-length array with flexible-array
On May 11, 2020 2:26:20 PM GMT-03:00, "Gustavo A. R. Silva" <gustavoars@...nel.org> wrote:
>On Mon, May 11, 2020 at 12:48:12PM -0300, Arnaldo Carvalho de Melo
>wrote:
>> Em Thu, May 07, 2020 at 02:06:15PM -0500, Gustavo A. R. Silva
>escreveu:
>> > The current codebase makes use of the zero-length array language
>> > extension to the C90 standard, but the preferred mechanism to
>declare
>> > variable-length types such as these ones is a flexible array
>member[1][2],
>> > introduced in C99:
>> >
>> > struct foo {
>> > int stuff;
>> > struct boo array[];
>> > };
>>
>> Can you split this into a kernel part and tools/ one? Also this is
>not
>> really just for "perf script", so please adjust the subject line too
>:-)
>>
>
>Sure thing. :)
>
>Is that OK if I use "perf: " for the tools part and "perf/x86: " for
>the
>kernel part?
perf tools: Summary
Since it touches multiple perf tools,
perf script: If it was only about 'perf script'
>
>Thanks
>--
>Gustavo
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
Powered by blists - more mailing lists