From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Wang Yugui <wangyugui@e16-tech.com>
Cc: stable@vger.kernel.org, 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, f.fainelli@gmail.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: Fri, 6 Oct 2023 12:12:55 +0200 [thread overview]
Message-ID: <2023100648-lizard-briskly-f6ac@gregkh> (raw)
In-Reply-To: <20231005081746.D7B7.409509F4@e16-tech.com>
On Thu, Oct 05, 2023 at 08:17:48AM +0800, Wang Yugui wrote:
> Hi,
>
> > 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.
>
> This 6.1.56-rc1 failed to build on rhel7 with dev-tool-set 8, but 6.1.55 works.
>
> Build error message:
> gcc: fatal error: no input files
> make[3]: *** [pmu-events/Build:33: pmu-events/pmu-events.o] Error 1
>
> After the revert of 'perf-build-update-build-rule-for-generated-files.patch'
> the build works again.
Offending patch dropped, thanks.
greg k-h
next prev parent reply other threads:[~2023-10-06 10:13 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
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 [this message]
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=2023100648-lizard-briskly-f6ac@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.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 \
--cc=wangyugui@e16-tech.com \
/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