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
Subject: Re: [PATCH 6.3 000/431] 6.3.13-rc1 review
Date: Sun, 9 Jul 2023 22:22:48 +0200	[thread overview]
Message-ID: <2023070935-circulate-elves-fa11@gregkh> (raw)
In-Reply-To: <CAEUSe7_dcPNEMqCbd6r+f_zJypQ196MSxigq6i+5eSh3=vvDOQ@mail.gmail.com>

On Sun, Jul 09, 2023 at 02:06:05PM -0600, Daniel Díaz wrote:
> Hello!
> 
> On Sun, 9 Jul 2023 at 05:18, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> > ------------------
> > Note, this is the LAST release for the 6.3.y kernel series.  After this
> > is released, it will be end-of-life.  Please move to the 6.4.y kernel
> > series at this point in time, OR let us know what is preventing that
> > from happening for you.
> > ------------------
> >
> > This is the start of the stable review cycle for the 6.3.13 release.
> > There are 431 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 Tue, 11 Jul 2023 11:14:03 +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.3.13-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.3.y
> > and the diffstat can be found below.
> >
> > thanks,
> >
> > greg k-h
> 
> There build regressions on Arm 32-bits, specifically omap1_defconfig:
> 
> -----8<-----
>   /builds/linux/arch/arm/mach-omap1/irq.c: In function 'omap1_init_irq':
>   /builds/linux/arch/arm/mach-omap1/irq.c:221:11: error: implicit
> declaration of function 'irq_domain_add_legacy'
> [-Werror=implicit-function-declaration]
>     domain = irq_domain_add_legacy(NULL, nr_irqs, irq_base, 0,
>              ^~~~~~~~~~~~~~~~~~~~~
>   /builds/linux/arch/arm/mach-omap1/irq.c:222:13: error:
> 'irq_domain_simple_ops' undeclared (first use in this function); did
> you mean 'irq_domain_chip_generic'?
>               &irq_domain_simple_ops, NULL);
>                ^~~~~~~~~~~~~~~~~~~~~
>                irq_domain_chip_generic
>   /builds/linux/arch/arm/mach-omap1/irq.c:222:13: note: each
> undeclared identifier is reported only once for each function it
> appears in
>   /builds/linux/arch/arm/mach-omap1/irq.c:250:23: error: implicit
> declaration of function 'irq_find_mapping'; did you mean
> 'iomem_get_mapping'? [-Werror=implicit-function-declaration]
>     d = irq_get_irq_data(irq_find_mapping(domain, omap_l2_irq));
>                          ^~~~~~~~~~~~~~~~
>                          iomem_get_mapping
>   cc1: some warnings being treated as errors
>   make[3]: *** [/builds/linux/scripts/Makefile.build:252:
> arch/arm/mach-omap1/irq.o] Error 1
> ----->8-----

Ick, sorry, let me go drop some patches and push out a -rc2.

thanks,

greg k-h

      reply	other threads:[~2023-07-09 20:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-09 11:09 [PATCH 6.3 000/431] 6.3.13-rc1 review Greg Kroah-Hartman
2023-07-09 11:10 ` [PATCH 6.3 085/431] sctp: add bpf_bypass_getsockopt proto callback Greg Kroah-Hartman
2023-07-09 20:06 ` [PATCH 6.3 000/431] 6.3.13-rc1 review Daniel Díaz
2023-07-09 20:22   ` Greg Kroah-Hartman [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=2023070935-circulate-elves-fa11@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --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