From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
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: Thu, 18 Apr 2024 22:06:46 -0300 [thread overview]
Message-ID: <ZiHDplDS5OuDvhMU@x1> (raw)
In-Reply-To: <ZiHAqDX0AQfsQbb6@x1>
On Thu, Apr 18, 2024 at 09:54:03PM -0300, Arnaldo Carvalho de Melo wrote:
> On Fri, Apr 19, 2024 at 09:17:17AM +1000, Stephen Rothwell wrote:
> > 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).
> I'm finishing some local tests here, will push perf-tools-next after
> that, some 30 minutes.
Ah, and again thanks for the report and follow up collaboration on
having these things sorted out, I'm sorry for not having this fixed
sooner, I'm taking notes to automate this type of test and have it done
before pushing branches publicly.
I just found it strange that when trying to reproduce this the problem
didn't manifested itself reliably, but then, ENOTIME to root cause this
so far, this (partial) revert is the best thing we can do now, so lets
go with it.
- Arnaldo
prev parent reply other threads:[~2024-04-19 1:06 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
2024-04-19 0:54 ` Arnaldo Carvalho de Melo
2024-04-19 1:06 ` Arnaldo Carvalho de Melo [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=ZiHDplDS5OuDvhMU@x1 \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=arnaldo.melo@gmail.com \
--cc=irogers@google.com \
--cc=kan.liang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).