mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Daniel Díaz" <daniel.diaz@linaro.org>
To: Sasha Levin <sashal@kernel.org>,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Cc: torvalds@linux-foundation.org, akpm@linux-foundation.org,
	linux@roeck-us.net, shuah@kernel.org, patches@kernelci.org,
	lkft-triage@lists.linaro.org, florian.fainelli@broadcom.com,
	pavel@denx.de, stephen.s.brennan@oracle.com
Subject: Re: [PATCH 5.15 000/309] 5.15.153-rc2 review
Date: Mon, 25 Mar 2024 13:11:29 -0600	[thread overview]
Message-ID: <1ca89b68-fe6b-4963-a33c-971fd7e1f0e6@linaro.org> (raw)
In-Reply-To: <20240325115928.1765766-1-sashal@kernel.org>

Hello!

On 25/03/24 5:59 a. m., Sasha Levin wrote:
> This is the start of the stable review cycle for the 5.15.153 release.
> There are 309 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 Mar 27 11:59:27 AM UTC 2024.
> Anything received after that time might be too late.
> 
> The whole patch series can be found in one patch at:
>          https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/patch/?id=linux-5.15.y&id2=v5.15.152
> or in the git tree and branch at:
>          git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.15.y
> and the diffstat can be found below.
> 
> Thanks,
> Sasha

We see other warnings here too, on Ar64, Arm32, x86, i386, MIPS, PowerPC, RISC-V, System/390, SuperH, SPARC, ARC, on multiple combinations of toolchain and kernel configs.

-----8<-----
   /builds/linux/kernel/printk/printk.c:261:13: warning: 'panic_in_progress' defined but not used [-Wunused-function]
     261 | static bool panic_in_progress(void)
         |             ^~~~~~~~~~~~~~~~~
----->8-----

Reverting this commit makes the warning disappear:

   commit d3ba3bc06ffa68aac04cf4f102ec882890a16015
   Author: Stephen Brennan <stephen.s.brennan@oracle.com>
   Date:   Wed Feb 2 09:18:18 2022 -0800

       printk: Add panic_in_progress helper
       
       [ Upstream commit 77498617857f68496b360081dde1a492d40c28b2 ]

Here's a reproducer:

   tuxmake --runtime podman --target-arch x86_64 --toolchain gcc-12 --kconfig tinyconfig


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

Greetings!

Daniel Díaz
daniel.diaz@linaro.org


  parent reply	other threads:[~2024-03-25 19:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-25 11:59 Sasha Levin
2024-03-25 17:53 ` Daniel Díaz
2024-03-25 17:59 ` SeongJae Park
2024-03-25 18:34 ` Florian Fainelli
2024-03-25 19:11 ` Daniel Díaz [this message]
2024-03-26  9:44 ` Ron Economos
2024-03-26 17:20 ` Shuah Khan
2024-03-26 18:33 ` Shreeya Patel
2024-03-27  1:50 ` Kelsey Steele
2024-03-27  8:39 ` Harshit Mogalapalli
2024-03-27 14:25   ` Greg Kroah-Hartman
2024-03-27 21:44   ` Guenter Roeck
2024-03-28  6:10     ` 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=1ca89b68-fe6b-4963-a33c-971fd7e1f0e6@linaro.org \
    --to=daniel.diaz@linaro.org \
    --cc=akpm@linux-foundation.org \
    --cc=florian.fainelli@broadcom.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lkft-triage@lists.linaro.org \
    --cc=patches@kernelci.org \
    --cc=pavel@denx.de \
    --cc=sashal@kernel.org \
    --cc=shuah@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=stephen.s.brennan@oracle.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®