All of lore.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.12.y] rust: kbuild: set `bindgen`'s Rust target version
Date: Sun, 15 Dec 2024 12:51:33 -0500	[thread overview]
Message-ID: <20241215123630-0a2c2266629f4f9e@stable.kernel.org> (raw)
In-Reply-To: <20241215145740.237008-1-ojeda@kernel.org>

[ Sasha's backport helper bot ]

Hi,

The upstream commit SHA1 provided is correct: 7a5f93ea5862da91488975acaa0c7abd508f192b


Status in newer kernel trees:
6.12.y | Not found

Note: The patch differs from the upstream commit:
---
1:  7a5f93ea5862 ! 1:  97fd2a891113 rust: kbuild: set `bindgen`'s Rust target version
    @@ Metadata
      ## Commit message ##
         rust: kbuild: set `bindgen`'s Rust target version
     
    +    commit 7a5f93ea5862da91488975acaa0c7abd508f192b upstream.
    +
         Each `bindgen` release may upgrade the list of Rust targets. For instance,
         currently, in their master branch [1], the latest ones are:
     
    @@ Commit message
     
      ## rust/Makefile ##
     @@ rust/Makefile: endif
    - # architecture instead of generating `usize`.
    - bindgen_c_flags_final = $(bindgen_c_flags_lto) -fno-builtin -D__BINDGEN__
    + 
    + bindgen_c_flags_final = $(bindgen_c_flags_lto) -D__BINDGEN__
      
     +# Each `bindgen` release may upgrade the list of Rust target versions. By
     +# default, the highest stable release in their list is used. Thus we need to set
    @@ rust/Makefile: endif
            cmd_bindgen = \
     -	$(BINDGEN) $< $(bindgen_target_flags) \
     +	$(BINDGEN) $< $(bindgen_target_flags) --rust-target 1.68 \
    - 		--use-core --with-derive-default --ctypes-prefix ffi --no-layout-tests \
    + 		--use-core --with-derive-default --ctypes-prefix core::ffi --no-layout-tests \
      		--no-debug '.*' --enable-function-attribute-detection \
      		-o $@ -- $(bindgen_c_flags_final) -DMODULE \
---

Results of testing on various branches:

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

      reply	other threads:[~2024-12-15 17:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-15  7:39 FAILED: patch "[PATCH] rust: kbuild: set `bindgen`'s Rust target version" failed to apply to 6.12-stable tree gregkh
2024-12-15 14:57 ` [PATCH 6.12.y] rust: kbuild: set `bindgen`'s Rust target version Miguel Ojeda
2024-12-15 17:51   ` 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=20241215123630-0a2c2266629f4f9e@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.