From: Florian Fainelli <f.fainelli@gmail.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
stable@vger.kernel.org, Ian Rogers <irogers@google.com>,
patches@lists.linux.dev, linux-kernel@vger.kernel.org,
torvalds@linux-foundation.org, akpm@linux-foundation.org,
linux@roeck-us.net, shuah@kernel.org, patches@kernelci.org,
lkft-triage@lists.linaro.org, pavel@denx.de,
jonathanh@nvidia.com, sudipm.mukherjee@gmail.com,
srw@sladewatkins.net, rwarsow@gmx.de, conor@kernel.org
Subject: Re: [PATCH 6.1 000/259] 6.1.56-rc1 review
Date: Wed, 4 Oct 2023 17:51:50 -0700 [thread overview]
Message-ID: <d2b80a6d-63c8-46ec-bf0f-83217a7c517d@gmail.com> (raw)
In-Reply-To: <CAM9d7chUnxjPdOwZZ0imYs+i8+dd9GL=O3gqJXzaRd1VGZJxBg@mail.gmail.com>
On 10/4/2023 1:19 PM, Namhyung Kim wrote:
> Hello,
>
> On Wed, Oct 4, 2023 at 12:33 PM Florian Fainelli <f.fainelli@gmail.com> wrote:
>>
>> +Namhyung, Ian,
>>
>> On 10/4/23 10:52, Greg Kroah-Hartman wrote:
>>> This is the start of the stable review cycle for the 6.1.56 release.
>>> There are 259 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 Fri, 06 Oct 2023 17:51:12 +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/v6.x/stable-review/patch-6.1.56-rc1.gz
>>> or in the git tree and branch at:
>>> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-6.1.y
>>> and the diffstat can be found below.
>>>
>>> thanks,
>>>
>>> greg k-h
>>
>> perf fails to build with:
>>
>> fixdep: error opening depfile:
>> /local/users/fainelli/buildroot/output/arm/build/linux-custom/tools/perf/pmu-events/.pmu-events.o.d:
>> No such file or directory
>> make[5]: *** [pmu-events/Build:33:
>> /local/users/fainelli/buildroot/output/arm/build/linux-custom/tools/perf/pmu-events/pmu-events.o]
>> Error 2
>> make[4]: *** [Makefile.perf:672:
>> /local/users/fainelli/buildroot/output/arm/build/linux-custom/tools/perf/pmu-events/pmu-events-in.o]
>> Error 2
>> make[3]: *** [Makefile.perf:240: sub-make] Error 2
>> make[2]: *** [Makefile:70: all] Error 2
>> make[1]: *** [package/pkg-generic.mk:294:
>> /local/users/fainelli/buildroot/output/arm/build/linux-tools/.stamp_built]
>> Error 2
>> make: *** [Makefile:27: _all] Error 2
>>
>> due a80fd00cb1a7793ead4d7c3fa7d3f1e898231c27 ("perf build: Update build
>> rule for generated files"). Reverting that commit fixes the build for me
>> and then all is good in terms of testing.
>
> I think it's ok to drop the patches if it's not applied
> cleanly.
AFAICT the patch applied cleanly. There was some bizarre interplay in
stable kernels prior to < 6.1 as reported here:
https://lore.kernel.org/all/dcb9997a-2e8a-5eb2-7a34-f8af418d4bf1@gmail.com/
https://lore.kernel.org/all/6a577578-8adb-aa70-1bf8-b1a4573152cf@gmail.com/
Does this make sense to you that on 6.1 which does have Ian's commit
00facc760903be6675870c2749e2cd72140e396e ("perf jevents: Switch build to
use jevents.py") that we would still get this build error somehow?
Thanks
--
Florian
next prev parent reply other threads:[~2023-10-05 0:52 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-04 17:52 [PATCH 6.1 000/259] 6.1.56-rc1 review Greg Kroah-Hartman
2023-10-04 19:33 ` Florian Fainelli
2023-10-04 20:19 ` Namhyung Kim
2023-10-05 0:51 ` Florian Fainelli [this message]
2023-10-05 5:15 ` Namhyung Kim
2023-10-06 10:12 ` Greg Kroah-Hartman
2023-10-05 0:17 ` Wang Yugui
2023-10-06 10:12 ` Greg Kroah-Hartman
2023-10-05 0:59 ` Shuah Khan
2023-10-05 1:32 ` SeongJae Park
2023-10-05 3:41 ` Bagas Sanjaya
2023-10-05 12:27 ` Pavel Machek
2023-10-06 12:55 ` Greg Kroah-Hartman
2023-10-05 13:57 ` Takeshi Ogasawara
2023-10-05 16:39 ` Naresh Kamboju
2023-10-05 17:24 ` Petr Vorel
2023-10-05 19:20 ` Naresh Kamboju
2023-10-06 6:41 ` Petr Vorel
2023-10-06 18:42 ` Daniel Díaz
2023-10-07 8:58 ` Greg Kroah-Hartman
2023-10-09 16:43 ` Naresh Kamboju
2023-10-05 18:40 ` Allen Pais
2023-10-05 22:17 ` Guenter Roeck
2023-10-06 7:30 ` Ron Economos
2023-10-06 9:32 ` Jon Hunter
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=d2b80a6d-63c8-46ec-bf0f-83217a7c517d@gmail.com \
--to=f.fainelli@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=conor@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=irogers@google.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=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@denx.de \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--cc=srw@sladewatkins.net \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--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