mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Daniel Díaz" <daniel.diaz@linaro.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>, stable@vger.kernel.org
Cc: 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 4.19 00/97] 4.19.300-rc1 review
Date: Fri, 24 Nov 2023 13:13:33 -0600	[thread overview]
Message-ID: <d48b5514-759f-47a0-b024-494ce87ec60f@linaro.org> (raw)
In-Reply-To: <20231124171934.122298957@linuxfoundation.org>

Hello!

On 24/11/23 11:49 a. m., Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.19.300 release.
> There are 97 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 Sun, 26 Nov 2023 17:19:17 +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.300-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-4.19.y
> and the diffstat can be found below.
> 
> thanks,
> 
> greg k-h

We see this failure on Arm32:
-----8<-----
   /builds/linux/drivers/tty/serial/meson_uart.c: In function 'meson_uart_probe':
   /builds/linux/drivers/tty/serial/meson_uart.c:728:13: error: 'struct uart_port' has no member named 'has_sysrq'
     728 |         port->has_sysrq = IS_ENABLED(CONFIG_SERIAL_MESON_CONSOLE);
         |             ^~
   make[4]: *** [/builds/linux/scripts/Makefile.build:303: drivers/tty/serial/meson_uart.o] Error 1
----->8-----

And this one on Arm64:
-----8<-----
   /builds/linux/kernel/profile.c: In function 'profile_dead_cpu':
   /builds/linux/kernel/profile.c:346:27: warning: the comparison will always evaluate as 'true' for the address of 'prof_cpu_mask' will never be NULL [-Waddress]
     346 |         if (prof_cpu_mask != NULL)
         |                           ^~
   /builds/linux/kernel/profile.c:49:22: note: 'prof_cpu_mask' declared here
      49 | static cpumask_var_t prof_cpu_mask;
         |                      ^~~~~~~~~~~~~
   /builds/linux/kernel/profile.c: In function 'profile_online_cpu':
   /builds/linux/kernel/profile.c:383:27: warning: the comparison will always evaluate as 'true' for the address of 'prof_cpu_mask' will never be NULL [-Waddress]
     383 |         if (prof_cpu_mask != NULL)
         |                           ^~
   /builds/linux/kernel/profile.c:49:22: note: 'prof_cpu_mask' declared here
      49 | static cpumask_var_t prof_cpu_mask;
         |                      ^~~~~~~~~~~~~
   /builds/linux/kernel/profile.c: In function 'profile_tick':
   /builds/linux/kernel/profile.c:413:47: warning: the comparison will always evaluate as 'true' for the address of 'prof_cpu_mask' will never be NULL [-Waddress]
     413 |         if (!user_mode(regs) && prof_cpu_mask != NULL &&
         |                                               ^~
   /builds/linux/kernel/profile.c:49:22: note: 'prof_cpu_mask' declared here
      49 | static cpumask_var_t prof_cpu_mask;
         |                      ^~~~~~~~~~~~~
----->8-----

Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>

Greetings!

Daniel Díaz
daniel.diaz@linaro.org


  reply	other threads:[~2023-11-24 19:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-24 17:49 Greg Kroah-Hartman
2023-11-24 19:13 ` Daniel Díaz [this message]
2023-11-25 11:20   ` Pavel Machek
2023-11-25 15:26     ` Greg Kroah-Hartman
2023-11-25 16:44       ` Pavel Machek
2023-11-25 15:43   ` Greg Kroah-Hartman

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=d48b5514-759f-47a0-b024-494ce87ec60f@linaro.org \
    --to=daniel.diaz@linaro.org \
    --cc=akpm@linux-foundation.org \
    --cc=conor@kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --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

all inboxes | Powered by JetHome®