public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Miguel Ojeda <ojeda@kernel.org>, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.14.y] scripts: generate_rust_analyzer: Add ffi crate
Date: Mon, 21 Apr 2025 22:15:51 -0400	[thread overview]
Message-ID: <20250421194247-50eb35a87a22ee4f@stable.kernel.org> (raw)
In-Reply-To: <20250421123827.3147434-1-ojeda@kernel.org>

[ Sasha's backport helper bot ]

Hi,

✅ All tests passed successfully. No issues detected.
No action required from the submitter.

The upstream commit SHA1 provided is correct: 05a2b0011c4b6cbbc9b577f6abebe4e9333b0cf6

WARNING: Author mismatch between patch and upstream commit:
Backport author: Miguel Ojeda<ojeda@kernel.org>
Commit author: Lukas Fischer<kernel@o1oo11oo.de>

Note: The patch differs from the upstream commit:
---
1:  05a2b0011c4b6 ! 1:  5869631cf792b scripts: generate_rust_analyzer: Add ffi crate
    @@ Metadata
      ## Commit message ##
         scripts: generate_rust_analyzer: Add ffi crate
     
    +    commit 05a2b0011c4b6cbbc9b577f6abebe4e9333b0cf6 upstream.
    +
         Commit d072acda4862 ("rust: use custom FFI integer types") did not
         update rust-analyzer to include the new crate.
     
    @@ Commit message
         Cc: stable@vger.kernel.org
         Link: https://lore.kernel.org/r/20250404125150.85783-2-kernel@o1oo11oo.de
         Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
    +    [ Fixed conflicts. - Miguel ]
    +    Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
     
      ## scripts/generate_rust_analyzer.py ##
     @@ scripts/generate_rust_analyzer.py: def generate_crates(srctree, objtree, sysroot_src, external_src, cfgs):
    -         cfg=["kernel"],
    +         ["core", "compiler_builtins"],
          )
      
     +    append_crate(
    @@ scripts/generate_rust_analyzer.py: def generate_crates(srctree, objtree, sysroot
      
     -    append_crate_with_generated("bindings", ["core"])
     -    append_crate_with_generated("uapi", ["core"])
    --    append_crate_with_generated("kernel", ["core", "macros", "build_error", "pin_init", "bindings", "uapi"])
    +-    append_crate_with_generated("kernel", ["core", "macros", "build_error", "bindings", "uapi"])
     +    append_crate_with_generated("bindings", ["core", "ffi"])
     +    append_crate_with_generated("uapi", ["core", "ffi"])
    -+    append_crate_with_generated("kernel", ["core", "macros", "build_error", "pin_init", "ffi", "bindings", "uapi"])
    ++    append_crate_with_generated("kernel", ["core", "macros", "build_error", "ffi", "bindings", "uapi"])
      
          def is_root_crate(build_file, target):
              try:
---

Results of testing on various branches:

| Branch                    | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.14.y       |  Success    |  Success   |

      reply	other threads:[~2025-04-22  2:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-21 11:24 FAILED: patch "[PATCH] scripts: generate_rust_analyzer: Add ffi crate" failed to apply to 6.14-stable tree gregkh
2025-04-21 12:38 ` [PATCH 6.14.y] scripts: generate_rust_analyzer: Add ffi crate Miguel Ojeda
2025-04-22  2:15   ` Sasha Levin [this message]

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=20250421194247-50eb35a87a22ee4f@stable.kernel.org \
    --to=sashal@kernel.org \
    --cc=ojeda@kernel.org \
    --cc=stable@vger.kernel.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