From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Arnaldo Carvalho de Melo <acme@kernel•org>
Cc: Arnaldo Carvalho de Melo <arnaldo.melo@gmail•com>,
Namhyung Kim <namhyung@kernel•org>,
Ian Rogers <irogers@google•com>, Kan Liang <kan.liang@intel•com>,
Adrian Hunter <adrian.hunter@intel•com>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: [PATCH][RFT] Re: linux-next: build failure after merge of the perf tree
Date: Fri, 19 Apr 2024 09:17:17 +1000 [thread overview]
Message-ID: <20240419091717.50ce0a81@canb.auug.org.au> (raw)
In-Reply-To: <ZiGRQZQGl0REHm9A@x1>
[-- Attachment #1: Type: text/plain, Size: 710 bytes --]
Hi Arnaldo,
On Thu, 18 Apr 2024 18:31:45 -0300 Arnaldo Carvalho de Melo <acme@kernel•org> wrote:
>
>
> And reproduced the problem, find below a patch that reverts the patch
> that removes tools/include/uapi/linux/stat.h, with it applied in the
> sequence above right after the merge of perf-tools-next it seems to
> work, i.e. it builds without problems.
>
> Can you please test this so that I can get it into perf-tools-next?
That works for me. Thanks for this.
Tested-by: Stephen Rothwell <sfr@canb•auug.org.au> # PowerPC le incermental build
I will apply that patch to linux-next today (if you don't have time to
update your tree before I merge it).
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-04-18 23:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-01 22:41 linux-next: build failure after merge of the perf tree Stephen Rothwell
2024-04-02 20:17 ` Arnaldo Carvalho de Melo
2024-04-12 15:22 ` Arnaldo Carvalho de Melo
2024-04-13 2:43 ` Stephen Rothwell
2024-04-18 21:31 ` [PATCH][RFT] " Arnaldo Carvalho de Melo
2024-04-18 23:17 ` Stephen Rothwell [this message]
2024-04-19 0:54 ` Arnaldo Carvalho de Melo
2024-04-19 1:06 ` Arnaldo Carvalho de Melo
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=20240419091717.50ce0a81@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=acme@kernel$(echo .)org \
--cc=adrian.hunter@intel$(echo .)com \
--cc=arnaldo.melo@gmail$(echo .)com \
--cc=irogers@google$(echo .)com \
--cc=kan.liang@intel$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=namhyung@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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