From: Arnaldo Melo <arnaldo.melo@gmail.com>
To: "Gustavo A. R. Silva" <gustavoars@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf script: Replace zero-length array with flexible-array
Date: Mon, 11 May 2020 15:48:55 -0300 [thread overview]
Message-ID: <AA4613D1-106B-4B4D-9470-EBEA2A527DC7@gmail.com> (raw)
In-Reply-To: <20200511172620.GA14618@embeddedor>
On May 11, 2020 2:26:20 PM GMT-03:00, "Gustavo A. R. Silva" <gustavoars@kernel.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.
next prev parent reply other threads:[~2020-05-11 18:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-07 19:06 Gustavo A. R. Silva
2020-05-08 12:37 ` Peter Zijlstra
2020-05-11 15:48 ` Arnaldo Carvalho de Melo
2020-05-11 17:26 ` Gustavo A. R. Silva
2020-05-11 18:48 ` Arnaldo Melo [this message]
2020-05-11 19:05 ` Gustavo A. R. Silva
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=AA4613D1-106B-4B4D-9470-EBEA2A527DC7@gmail.com \
--to=arnaldo.melo@gmail.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=gustavoars@kernel.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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
all inboxes | Powered by JetHome®