From: Miguel Ojeda <ojeda@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Miguel Ojeda" <ojeda@kernel.org>,
"Wedson Almeida Filho" <wedsonaf@gmail.com>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Rust fixes for 6.3-rc1
Date: Fri, 3 Mar 2023 22:21:05 +0100 [thread overview]
Message-ID: <20230303212105.78945-1-ojeda@kernel.org> (raw)
Hi Linus,
Please pull this build error fix for Rust: there was a change during
the merge window to a C header parsed by the Rust bindings generator,
introducing a type that it does not handle well. The fix tells
the generator to treat the type as opaque (for now).
It has been only a day on linux-next, but it is straightforward and
it would be nice to have in v6.3-rc1.
I have other fixes planned for this cycle, but I will let those sit
in linux-next for a while and send them after v6.3-rc1.
No conflicts expected. No changes to the C side.
Cheers,
Miguel
The following changes since commit c9c3395d5e3dcc6daee66c6908354d47bf98cb0c:
Linux 6.2 (2023-02-19 14:24:22 -0800)
are available in the Git repository at:
https://github.com/Rust-for-Linux/linux tags/rust-fixes-6.3-rc1
for you to fetch changes up to 3098cb655e7c9ea1c2919e61234f63ebaab6bb21:
rust: bindgen: Add `alt_instr` as opaque type (2023-03-02 22:44:15 +0100)
----------------------------------------------------------------
Rust fixes for 6.3-rc1
A single build error fix: there was a change during the merge window
to a C header parsed by the Rust bindings generator, introducing a
type that it does not handle well. The fix tells the generator to
treat the type as opaque (for now).
----------------------------------------------------------------
Arnaldo Carvalho de Melo (1):
rust: bindgen: Add `alt_instr` as opaque type
rust/bindgen_parameters | 1 +
1 file changed, 1 insertion(+)
next reply other threads:[~2023-03-03 21:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-03 21:21 Miguel Ojeda [this message]
2023-03-03 23:04 ` [GIT PULL] Rust fixes for 6.3-rc1 pr-tracker-bot
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=20230303212105.78945-1-ojeda@kernel.org \
--to=ojeda@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=wedsonaf@gmail.com \
/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