All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Florian Fainelli <florian.fainelli@broadcom.com>,
	linux-kernel@vger.kernel.org, mmayer@broadcom.com,
	bcm-kernel-feedback-list@broadcom.com,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Namhyung Kim <namhyung@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Jiri Olsa <jolsa@kernel.org>,
	Adrian Hunter <adrian.hunter@intel.com>,
	James Clark <james.clark@linaro.org>,
	"open list:PERFORMANCE EVENTS SUBSYSTEM"
	<linux-perf-users@vger.kernel.org>
Subject: Re: [PATCH] perf trace beauty fcntl: Fix build with older kernel headers
Date: Fri, 15 May 2026 08:30:18 -0300	[thread overview]
Message-ID: <agcDysX6_-FunmuX@x1> (raw)
In-Reply-To: <CAP-5=fXfwAXo1_FyS=ZZgtBaP0o5QNxz=1x9EFz+m+4gU8tnZQ@mail.gmail.com>

On Wed, May 13, 2026 at 04:13:58PM -0700, Ian Rogers wrote:
> On Wed, May 13, 2026 at 2:56 PM Florian Fainelli <florian.fainelli@broadcom.com> wrote:

> > On 5/13/26 13:58, Ian Rogers wrote:
> > > On Wed, May 13, 2026 at 12:23 PM Florian Fainelli <florian.fainelli@broadcom.com> wrote:
> > >> Toolchains with older kernel headers that do not include upstream commit
> > >> c75b1d9421f80f4143e389d2d50ddfc8a28c8c35 ("fs: add fcntl() interface for
> > >> setting/getting write life time hints") will now fail to build perf due
> > >> to missing definitions for
> > >> F_GET_RW_HINT/F_SET_RW_HINT/F_GET_FILE_RW_HINT/F_SET_FILE_RW_HINT.

> > >> Provide a fallback definition for these when they are not already
> > >> defined.

> > > This seems fine but the commit you mention was added to Linux 4.13. Is
> > > there a reason you've run into this problem? The oldest active LTS
> > > kernel is 4.19.

> > The toolchain I am using is still on kernel headers 4.9.x, I am
> > cognizant this is a very old set of kernel headers, this is specific and
> > unique to building for MIPS, our ARM/ARM64 targets are using more modern
> > components.

> Sgtm. I have some libunwind clean up for MIPS that I'll add you to, in
> case it is of interest since I can't test it myself :-)
 
> For this patch:
> Reviewed-by: Ian Rogers <irogers@google.com>

Thanks, applied to perf-tools-next, for v7.2.

- ARnaldo

  reply	other threads:[~2026-05-15 11:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-13 19:23 [PATCH] perf trace beauty fcntl: Fix build with older kernel headers Florian Fainelli
2026-05-13 20:58 ` Ian Rogers
2026-05-13 21:56   ` Florian Fainelli
2026-05-13 23:13     ` Ian Rogers
2026-05-15 11:30       ` Arnaldo Carvalho de Melo [this message]
2026-05-14 15:56 ` Namhyung Kim
2026-05-14 16:37   ` Ian Rogers
2026-05-14 16:57     ` Florian Fainelli
2026-05-14 17:13       ` Ian Rogers

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=agcDysX6_-FunmuX@x1 \
    --to=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=florian.fainelli@broadcom.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=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=mmayer@broadcom.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.