public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Daniel Díaz" <daniel.diaz@linaro.org>
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, apatel@ventanamicro.com
Subject: Re: [PATCH 5.10 00/95] 5.10.200-rc1 review
Date: Tue, 7 Nov 2023 21:24:08 +0100	[thread overview]
Message-ID: <2023110700-clad-matter-31bf@gregkh> (raw)
In-Reply-To: <CAEUSe7_g2LbOkb6BqqdPha4SX4669O33H0a04sJ7AfbR1wfA_w@mail.gmail.com>

On Mon, Nov 06, 2023 at 12:14:21PM -0600, Daniel Díaz wrote:
> Hello!
> 
> On Mon, 6 Nov 2023 at 11:53, Daniel Díaz <daniel.diaz@linaro.org> wrote:
> > On 06/11/23 7:03 a. m., Greg Kroah-Hartman wrote:
> > > This is the start of the stable review cycle for the 5.10.200 release.
> > > There are 95 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, 08 Nov 2023 13:02:46 +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/v5.x/stable-review/patch-5.10.200-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-5.10.y
> > > and the diffstat can be found below.
> > >
> > > thanks,
> > >
> > > greg k-h
> >
> > There seems to be a problem building for RISC-V with GCC 8, 12, and Clang 17. This is with defconfig, allnoconfig, tinyconfig:
> >
> > -----8<-----
> > /builds/linux/drivers/irqchip/irq-riscv-intc.c: In function 'riscv_intc_init':
> > /builds/linux/drivers/irqchip/irq-riscv-intc.c:119:17: error: implicit declaration of function 'fwnode_dev_initialized'; did you mean 'zone_is_initialized'? [-Werror=implicit-function-declaration]
> >    119 |                 fwnode_dev_initialized(of_fwnode_handle(node), true);
> >        |                 ^~~~~~~~~~~~~~~~~~~~~~
> >        |                 zone_is_initialized
> > cc1: some warnings being treated as errors
> > make[3]: *** [/builds/linux/scripts/Makefile.build:286: drivers/irqchip/irq-riscv-intc.o] Error 1
> > make[3]: Target '__build' not remade because of errors.
> > make[2]: *** [/builds/linux/scripts/Makefile.build:503: drivers/irqchip] Error 2
> > make[2]: Target '__build' not remade because of errors.
> > make[1]: *** [/builds/linux/Makefile:1832: drivers] Error 2
> > make[1]: Target '__all' not remade because of errors.
> > make: *** [Makefile:192: __sub-make] Error 2
> > make: Target '__all' not remade because of errors.
> > ----->8-----
> >
> > Currently bisecting.
> 
> -----8<-----
> Bisection done!
> First commit presenting NEW behaviour: 6751b1fbf98ba2c40bbdda22e2e6714a9c27b91b
> 
> commit 6751b1fbf98ba2c40bbdda22e2e6714a9c27b91b
> Author: Anup Patel <apatel@ventanamicro.com>
> Date:   Tue Oct 3 10:13:51 2023 +0530
> 
>     irqchip/riscv-intc: Mark all INTC nodes as initialized
> 
>     [ Upstream commit e13cd66bd821be417c498a34928652db4ac6b436 ]
> ----->8-----
> 
> Reverting that commit makes the build happy again.

Thanks, will go drop that now.

greg k-h

  reply	other threads:[~2023-11-07 20:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-06 13:03 [PATCH 5.10 00/95] 5.10.200-rc1 review Greg Kroah-Hartman
2023-11-06 17:37 ` Florian Fainelli
2023-11-07 20:22   ` Greg Kroah-Hartman
2023-11-06 17:53 ` Daniel Díaz
2023-11-06 18:14   ` Daniel Díaz
2023-11-07 20:24     ` Greg Kroah-Hartman [this message]
2023-11-06 21:30   ` Pavel Machek
2023-11-06 21:50 ` Pavel Machek
2023-11-07 11:34   ` Pavel Machek
2023-11-07  9:08 ` Dominique Martinet
2023-11-07 11:43 ` Jon Hunter
2023-11-07 15:40 ` Shuah Khan
2023-11-07 18:02 ` Naresh Kamboju
2023-11-07 18:57 ` Guenter Roeck

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=2023110700-clad-matter-31bf@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=apatel@ventanamicro.com \
    --cc=conor@kernel.org \
    --cc=daniel.diaz@linaro.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 \
    /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