From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: open list <linux-kernel@vger.kernel.org>,
Shuah Khan <shuah@kernel.org>,
Florian Fainelli <f.fainelli@gmail.com>,
patches@kernelci.org, lkft-triage@lists.linaro.org,
Jon Hunter <jonathanh@nvidia.com>,
linux-stable <stable@vger.kernel.org>,
Pavel Machek <pavel@denx.de>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Guenter Roeck <linux@roeck-us.net>,
Namhyung Kim <namhyung@kernel.org>, Jiri Olsa <jolsa@redhat.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Andi Kleen <ak@linux.intel.com>, Ian Rogers <irogers@google.com>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH 4.19 000/420] 4.19.198-rc2 review
Date: Tue, 20 Jul 2021 08:21:29 +0200 [thread overview]
Message-ID: <YPZraezaAgdBNPSp@kroah.com> (raw)
In-Reply-To: <CA+G9fYtAN7y5Z82nO59daxD=AtYOyu2J7ECFjY2P64JR9Fqifg@mail.gmail.com>
On Tue, Jul 20, 2021 at 11:25:22AM +0530, Naresh Kamboju wrote:
> On Tue, 20 Jul 2021 at 00:15, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> >
> > This is the start of the stable review cycle for the 4.19.198 release.
> > There are 420 patches in this series, all will be posted as a response
> > to this one. If anyone has any issues with these being applied, please
> > let me know.
> >
> > Responses should be made by Wed, 21 Jul 2021 18:42:43 +0000.
> > Anything received after that time might be too late.
> >
> > The whole patch series can be found in one patch at:
> > https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.19.198-rc2.gz
> > or in the git tree and branch at:
> > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-4.19.y
> > and the diffstat can be found below.
> >
> > thanks,
> >
> > greg k-h
>
> Perf fails to compile in 4.19 on Arm, Arm64, i386 and x86 with gcc 7.3
> It was also reported on 5.4.134-rc2.
>
> perf-1.0/perf-in.o: In function `tasks_setup':
> tools/perf/builtin-report.c:664: undefined reference to `process_attr'
> perf-in.o: In function `stats_setup':
> tools/perf/builtin-report.c:644: undefined reference to `process_attr'
>
> Bisection points to ee7531fb817c ("perf report: Fix --task and --stat
> with pipe input" [upstream commit
> 892ba7f18621a02af4428c58d97451f64685dba4]).
>
>
> > Namhyung Kim <namhyung@kernel.org>
> > perf report: Fix --task and --stat with pipe input
>
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
Thanks, now dropped from all branches.
greg k-h
next prev parent reply other threads:[~2021-07-20 6:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-19 18:45 [PATCH 4.19 000/420] 4.19.198-rc2 review Greg Kroah-Hartman
2021-07-19 20:46 ` Pavel Machek
2021-07-20 0:31 ` Shuah Khan
2021-07-20 5:55 ` Naresh Kamboju
2021-07-20 6:21 ` Greg Kroah-Hartman [this message]
2021-07-20 10:05 ` Sudip Mukherjee
2021-07-20 12:20 ` Samuel Zou
2021-07-20 20:09 ` Guenter Roeck
2021-07-21 9:19 ` Naresh Kamboju
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=YPZraezaAgdBNPSp@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=acme@redhat.com \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=f.fainelli@gmail.com \
--cc=irogers@google.com \
--cc=jolsa@redhat.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=namhyung@kernel.org \
--cc=naresh.kamboju@linaro.org \
--cc=patches@kernelci.org \
--cc=pavel@denx.de \
--cc=peterz@infradead.org \
--cc=shuah@kernel.org \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).