From: Namhyung Kim <namhyung@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
James Clark <james.clark@linaro.org>,
Chun-Tse Shao <ctshao@google.com>,
Swapnil Sapkal <swapnil.sapkal@amd.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
Ian Rogers <irogers@google.com>
Subject: Re: [PATCH v5] perf data: Clean up use_stdio and structures
Date: Thu, 09 Apr 2026 09:46:18 -0700 [thread overview]
Message-ID: <177575317842.128404.2482986120241211182.b4-ty@kernel.org> (raw)
In-Reply-To: <20260408203858.100855-1-irogers@google.com>
On Wed, 08 Apr 2026 13:38:58 -0700, Ian Rogers wrote:
> use_stdio was associated with struct perf_data and not perf_data_file
> meaning there was implicit use of fd rather than fptr that may not be
> safe. For example, in perf_data_file__write. Reorganize perf_data_file
> to better abstract use_stdio, add kernel-doc and more consistently use
> perf_data__ accessors so that use_stdio is better respected.
>
>
> [...]
Applied to perf-tools-next, thanks!
Best regards,
Namhyung
prev parent reply other threads:[~2026-04-09 16:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-08 0:14 [PATCH v2] perf data: Clean up use_stdio and structures Ian Rogers
2026-04-08 0:37 ` sashiko-bot
2026-04-08 6:47 ` [PATCH v3] " Ian Rogers
2026-04-08 7:06 ` sashiko-bot
2026-04-08 7:38 ` [PATCH v4] " Ian Rogers
2026-04-08 7:57 ` sashiko-bot
2026-04-08 20:38 ` [PATCH v5] " Ian Rogers
2026-04-09 16:46 ` Namhyung Kim [this message]
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=177575317842.128404.2482986120241211182.b4-ty@kernel.org \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=ctshao@google.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=swapnil.sapkal@amd.com \
/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