mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Miguel Ojeda <ojeda@kernel.org>
To: gregkh@linuxfoundation.org
Cc: akpm@linux-foundation.org, broonie@kernel.org, conor@kernel.org,
	f.fainelli@gmail.com, hargar@microsoft.com, jonathanh@nvidia.com,
	linux-kernel@vger.kernel.org, linux@roeck-us.net,
	lkft-triage@lists.linaro.org, patches@kernelci.org,
	patches@lists.linux.dev, pavel@denx.de, rwarsow@gmx.de,
	shuah@kernel.org, srw@sladewatkins.net, stable@vger.kernel.org,
	sudipm.mukherjee@gmail.com, torvalds@linux-foundation.org
Subject: Re: [PATCH 6.12 000/512] 6.12.34-rc1 review
Date: Wed, 18 Jun 2025 14:57:10 +0200	[thread overview]
Message-ID: <20250618125710.1920658-1-ojeda@kernel.org> (raw)
In-Reply-To: <20250617152419.512865572@linuxfoundation.org>

On Tue, 17 Jun 2025 17:19:26 +0200 Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
>
> This is the start of the stable review cycle for the 6.12.34 release.
> There are 512 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 Thu, 19 Jun 2025 15:22:45 +0000.
> Anything received after that time might be too late.

For arm64, with Clang 18, I got:

     drivers/thermal/mediatek/lvts_thermal.c:262:13: error: unused function 'lvts_debugfs_exit' [-Werror,-Wunused-function]
      262 | static void lvts_debugfs_exit(struct lvts_domain *lvts_td) { }
          |             ^~~~~~~~~~~~~~~~~
    1 error generated.

I assume the reason is that `CONFIG_MTK_LVTS_THERMAL_DEBUGFS=n`.

In mainline I don't see it. I think we need commit 3159c96ac2cb
("thermal/drivers/mediatek/lvts: Remove unused lvts_debugfs_exit").

It cherry-picks cleanly.

Otherwise, boot-tested under QEMU for Rust x86_64 and riscv64;
built-tested for loongarch64.

Thanks!

Cheers,
Miguel

  parent reply	other threads:[~2025-06-18 12:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-17 15:19 Greg Kroah-Hartman
2025-06-17 15:24 ` [PATCH 6.12 297/512] perf symbol: Fix use-after-free in filename__read_build_id Greg Kroah-Hartman
2025-06-17 16:42 ` [PATCH 6.12 000/512] 6.12.34-rc1 review Florian Fainelli
2025-06-17 19:56 ` Pavel Machek
2025-06-17 21:18 ` Shuah Khan
2025-06-18  6:27 ` Ron Economos
2025-06-18  6:39 ` Peter Schneider
2025-06-18  6:41 ` Jon Hunter
2025-06-18 10:32 ` Naresh Kamboju
2025-06-18 12:57 ` Miguel Ojeda [this message]
2025-06-19  4:27   ` Greg KH
2025-06-18 13:31 ` Brett Mastbergen
2025-06-18 18:02 ` Hardik Garg
2025-06-18 18:14 ` Markus Reichelt
2025-06-19  6:47 ` Harshit Mogalapalli
2025-06-19 12:26 ` Mark Brown

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=20250618125710.1920658-1-ojeda@kernel.org \
    --to=ojeda@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@kernel.org \
    --cc=conor@kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hargar@microsoft.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

all inboxes | Powered by JetHome®