linux-stable.git/Makefile, branch v6.12.90

Linux 6.12.90

2026-05-17T15:14:35+00:00

Link: https://lore.kernel.org/r/20260515154653.469907118@linuxfoundation.org
Tested-by: Florian Fainelli 
Tested-by: Pavel Machek (CIP) 
Tested-by: Shuah Khan 
Tested-by: Peter Schneider 
Tested-by: Miguel Ojeda 
Tested-by: Salvatore Bonaccorso 
Tested-by: Mark Brown 
Tested-by: Brett A C Sheffield 
Link: https://lore.kernel.org/r/20260516102210.570453769@linuxfoundation.org
Tested-by: Brett A C Sheffield 
Tested-by: Peter Schneider 
Tested-by: Ron Economos 
Tested-by: Miguel Ojeda 
Tested-by: Wentao Guan 
Signed-off-by: Greg Kroah-Hartman

rust: allow `clippy::collapsible_if` globally

2026-05-17T15:14:34+00:00

commit 2adc8664018c1cc595c7c0c98474a33c7fe32a85 upstream.

Similar to `clippy::collapsible_match` (globally allowed in the previous
commit), the `clippy::collapsible_if` lint [1] can make code harder to
read in certain cases.

Thus just let developers decide on their own.

In addition, remove the existing `expect` we had.

Cc: stable@vger.kernel.org # Needed in 6.12.y and later (Rust is pinned in older LTSs).
Suggested-by: Gary Guo 
Link: https://lore.kernel.org/rust-for-linux/DGROP5CHU1QZ.1OKJRAUZXE9WC@garyguo.net/
Link: https://rust-lang.github.io/rust-clippy/master/index.html#collapsible_if [1]
Reviewed-by: Gary Guo 
Link: https://patch.msgid.link/20260426144201.227108-2-ojeda@kernel.org
Signed-off-by: Miguel Ojeda 
Signed-off-by: Greg Kroah-Hartman

rust: allow `clippy::collapsible_match` globally

2026-05-17T15:14:34+00:00

commit 838d852da8503372f3a1779bfbd1ccb93153ab4e upstream.

The `clippy::collapsible_match` lint [1] can make code harder to read
in certain cases [2], e.g.

      CLIPPY P rust/libmacros.so - due to command line change
    warning: this `if` can be collapsed into the outer `match`
      --> rust/pin-init/internal/src/helpers.rs:91:17
       |
    91 | /                 if nesting == 1 {
    92 | |                     impl_generics.push(tt.clone());
    93 | |                     impl_generics.push(tt);
    94 | |                     skip_until_comma = false;
    95 | |                 }
       | |_________________^
       |
       = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#collapsible_match
       = note: `-W clippy::collapsible-match` implied by `-W clippy::all`
       = help: to override `-W clippy::all` add `#[allow(clippy::collapsible_match)]`
    help: collapse nested if block
       |
    90 ~             TokenTree::Punct(p) if skip_until_comma && p.as_char() == ','
    91 ~                 && nesting == 1 => {
    92 |                     impl_generics.push(tt.clone());
    93 |                     impl_generics.push(tt);
    94 |                     skip_until_comma = false;
    95 ~                 }
       |

The lint does not have much upside -- when the suggestion may be a good
one, it would still read fine when nested anyway. And it is the kind of
lint that may easily bias people to just apply the suggestion instead
of allowing it.

[ In addition, as Gary points out [3], the suggestion is also wrong [4] and
  in the process of being fixed [5], possibly for Rust 1.97.0:

  Link: https://lore.kernel.org/rust-for-linux/DI3YV94TH9I3.1SOHW51552497@garyguo.net/ [3]
  Link: https://github.com/rust-lang/rust-clippy/issues/16875 [4]
  Link: https://github.com/rust-lang/rust-clippy/pull/16878 [5]

    - Miguel ]

Thus just let developers decide on their own.

Cc: stable@vger.kernel.org # Needed in 6.12.y and later (Rust is pinned in older LTSs).
Link: https://rust-lang.github.io/rust-clippy/master/index.html#collapsible_match [1]
Link: https://lore.kernel.org/rust-for-linux/CANiq72nWYJna_hdFxjQCQZK6yJBrr1Mb86iKavivV0U0BgufeA@mail.gmail.com/ [2]
Reviewed-by: Gary Guo 
Link: https://patch.msgid.link/20260426144201.227108-1-ojeda@kernel.org
Signed-off-by: Miguel Ojeda 
Signed-off-by: Greg Kroah-Hartman

Linux 6.12.89

2026-05-15T12:51:08+00:00

Signed-off-by: Greg Kroah-Hartman

Linux 6.12.88

2026-05-14T13:29:29+00:00

Link: https://lore.kernel.org/r/20260512173932.810559588@linuxfoundation.org
Tested-by: Salvatore Bonaccorso 
Tested-by: Pavel Machek (CIP) 
Tested-by: Peter Schneider 
Tested-by: Dominique Martinet 
Tested-by: Brett A C Sheffield 
Tested-by: Francesco Dolcini 
Tested-by: Barry K. Nathan 
Tested-by: Mark Brown 
Tested-by: Shuah Khan 
Tested-by: Harshit Mogalapalli 
Link: https://lore.kernel.org/r/20260513153743.326058350@linuxfoundation.org
Tested-by: Brett A C Sheffield 
Tested-by: Florian Fainelli 
Tested-by: Ron Economos 
Tested-by: Mark Brown 
Tested-by: Dominique Martinet 
Tested-by: Francesco Dolcini 
Tested-by: Miguel Ojeda 
Signed-off-by: Greg Kroah-Hartman

Linux 6.12.87

2026-05-08T06:39:25+00:00

Signed-off-by: Greg Kroah-Hartman

Linux 6.12.86

2026-05-07T04:09:48+00:00

Link: https://lore.kernel.org/r/20260504135130.169210693@linuxfoundation.org
Tested-by: Brett A C Sheffield 
Tested-by: Peter Schneider 
Tested-by: Florian Fainelli 
Tested-by: Salvatore Bonaccorso 
Tested-by: Francesco Dolcini 
Tested-by: Ron Economos 
Tested-by: Miguel Ojeda 
Tested-by: Mark Brown 
Tested-by: Shuah Khan 
Tested-by: Barry K. Nathan 
Signed-off-by: Greg Kroah-Hartman

kbuild: rust: allow `clippy::uninlined_format_args`

2026-05-07T04:09:25+00:00

commit 10eea3c147141c90cf409b8df56d245c9d7f88d9 upstream.

Clippy in Rust 1.88.0 (only) reports [1]:

    warning: variables can be used directly in the `format!` string
       --> rust/macros/module.rs:112:23
        |
    112 |         let content = format!("{param}:{content}", param = param, content = content);
        |                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        |
        = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#uninlined_format_args
        = note: `-W clippy::uninlined-format-args` implied by `-W clippy::all`
        = help: to override `-W clippy::all` add `#[allow(clippy::uninlined_format_args)]`
    help: change this to
        |
    112 -         let content = format!("{param}:{content}", param = param, content = content);
    112 +         let content = format!("{param}:{content}");

    warning: variables can be used directly in the `format!` string
       --> rust/macros/module.rs:198:14
        |
    198 |         t => panic!("Unsupported parameter type {}", t),
        |              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        |
        = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#uninlined_format_args
        = note: `-W clippy::uninlined-format-args` implied by `-W clippy::all`
        = help: to override `-W clippy::all` add `#[allow(clippy::uninlined_format_args)]`
    help: change this to
        |
    198 -         t => panic!("Unsupported parameter type {}", t),
    198 +         t => panic!("Unsupported parameter type {t}"),
        |

The reason it only triggers in that version is that the lint was moved
from `pedantic` to `style` in Rust 1.88.0 and then back to `pedantic`
in Rust 1.89.0 [2][3].

In the first case, the suggestion is fair and a pure simplification, thus
we will clean it up separately.

To keep the behavior the same across all versions, and since the lint
does not work for all macros (e.g. custom ones like `pr_info!`), disable
it globally.

Cc: stable@vger.kernel.org # Needed in 6.12.y and later (Rust is pinned in older LTSs).
Link: https://lore.kernel.org/rust-for-linux/CANiq72=drAtf3y_DZ-2o4jb6Az9J3Yj4QYwWnbRui4sm4AJD3Q@mail.gmail.com/ [1]
Link: https://github.com/rust-lang/rust-clippy/pull/15287 [2]
Link: https://github.com/rust-lang/rust-clippy/issues/15151 [3]
Link: https://patch.msgid.link/20260331205849.498295-1-ojeda@kernel.org
Signed-off-by: Miguel Ojeda 
Signed-off-by: Greg Kroah-Hartman

Linux 6.12.85

2026-04-30T09:14:47+00:00

Signed-off-by: Greg Kroah-Hartman

Linux 6.12.84

2026-04-27T13:24:26+00:00

Link: https://lore.kernel.org/r/20260424132411.427029259@linuxfoundation.org
Tested-by: Peter Schneider 
Tested-by: Pavel Machek (CIP) 
Tested-by: Florian Fainelli 
Tested-by: Mark Brown 
Tested-by: Shuah Khan 
Tested-by: Barry K. Nathan 
Tested-by: Christian Van 
Tested-by: Brett A C Sheffield 
Tested-by: Miguel Ojeda 
Tested-by: Ron Economos 
Tested-by: Francesco Dolcini 
Tested-by: Salvatore Bonaccorso 
Tested-by: Harshit Mogalapalli 
Signed-off-by: Greg Kroah-Hartman