public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Miguel Ojeda <ojeda@kernel.org>
Cc: achill@achill.org, 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@nabladev.com, rwarsow@gmx.de, shuah@kernel.org,
	sr@sladewatkins.com, stable@vger.kernel.org,
	sudipm.mukherjee@gmail.com, torvalds@linux-foundation.org,
	Benno Lossin <lossin@kernel.org>, Gary Guo <gary@garyguo.net>
Subject: Re: [PATCH 6.12 000/244] 6.12.80-rc1 review
Date: Thu, 2 Apr 2026 15:38:10 +0200	[thread overview]
Message-ID: <2026040254-spoiled-refinance-5b48@gregkh> (raw)
In-Reply-To: <20260402132540.124376-1-ojeda@kernel.org>

On Thu, Apr 02, 2026 at 03:25:40PM +0200, Miguel Ojeda wrote:
> On Tue, 31 Mar 2026 18:19:10 +0200 Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
> >
> > This is the start of the stable review cycle for the 6.12.80 release.
> > There are 244 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, 02 Apr 2026 16:16:56 +0000.
> > Anything received after that time might be too late.
> 
> Boot-tested under QEMU for Rust x86_64, arm64 and riscv64; built-tested
> for loongarch64:
> 
> Tested-by: Miguel Ojeda <ojeda@kernel.org>
> 
> There are a bunch of `CLIPPY=1` warnings (errors with `CONFIG_WERROR`)
> like this one on the pin-init change:
> 
>     warning: unsafe block missing a safety comment
>         --> rust/kernel/init/macros.rs:1015:25
>          |
>     1015 |                         unsafe { ::core::pin::Pin::new_unchecked(slot) }
>          |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>          |
>         ::: rust/kernel/block/mq/tag_set.rs:27:1
>          |
>     27   | #[pin_data(PinnedDrop)]
>          | ----------------------- in this procedural macro expansion
>          |
>          = help: consider adding a safety comment on the preceding line
>          = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#undocumented_unsafe_blocks
>          = note: requested on the command line with `-W clippy::undocumented-unsafe-blocks`
>          = note: this warning originates in the macro `$crate::__pin_data` which comes from the expansion of the attribute macro `pin_data` (in Nightly builds, run with -Z macro-backtrace for more info)
> 
> It is not a huge deal, since they are just `CLIPPY=1` warnings, but we
> nevertheless try to keep them clean.
> 
> Apart from that, the rest looks OK.
> 
> Cc: Benno Lossin <lossin@kernel.org>
> Cc: Gary Guo <gary@garyguo.net>

Ok, I can live with clippy warnings, but will gladly take a fix-up patch
to resolve them :)

thanks,

greg k-h

  reply	other threads:[~2026-04-02 13:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-31 16:19 [PATCH 6.12 000/244] 6.12.80-rc1 review Greg Kroah-Hartman
2026-04-01  1:56 ` Barry K. Nathan
2026-04-01  3:31 ` Peter Schneider
2026-04-01  7:28 ` Brett A C Sheffield
2026-04-01  9:19 ` Jon Hunter
2026-04-01  9:29 ` Ron Economos
2026-04-01 11:40 ` Francesco Dolcini
2026-04-01 16:20 ` Shuah Khan
2026-04-01 17:39 ` Mark Brown
2026-04-02 10:49 ` Harshit Mogalapalli
2026-04-02 13:25 ` Miguel Ojeda
2026-04-02 13:38   ` Greg KH [this message]
2026-04-02 22:51 ` Florian Fainelli
2026-04-07 11:56 ` Pavel Machek

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=2026040254-spoiled-refinance-5b48@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=achill@achill.org \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@kernel.org \
    --cc=conor@kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=gary@garyguo.net \
    --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=lossin@kernel.org \
    --cc=ojeda@kernel.org \
    --cc=patches@kernelci.org \
    --cc=patches@lists.linux.dev \
    --cc=pavel@nabladev.com \
    --cc=rwarsow@gmx.de \
    --cc=shuah@kernel.org \
    --cc=sr@sladewatkins.com \
    --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