From: "Danilo Krummrich" <dakr@kernel.org>
To: "John Hubbard" <jhubbard@nvidia.com>
Cc: "nova-gpu@lists.linux.dev" <nova-gpu@lists.linux.dev>,
"Alexandre Courbot" <acourbot@nvidia.com>,
"rust-for-linux@vger.kernel.org" <rust-for-linux@vger.kernel.org>
Subject: Re: drm-rust-next needs a commit from rust-fixes
Date: Wed, 04 Nov 2026 01:10:57 +0100 [thread overview]
Message-ID: <DMLZOJTIQ2N6.1WNIKHGVV3U7T@kernel.org> (raw)
In-Reply-To: <211cc191-828d-4494-92c4-168906a0ede7@nvidia.com>
On Wed Nov 4, 2026 at 12:25 AM CET, John Hubbard wrote:
> We still need the fix [1] for this problem applied to drm-rust-next,
> as of today's (Nov 3, 2026) branch, anyway:
We can't apply a duplicate of that commit to drm-rust-next, but I will backmerge
-rc2 (which should contain the fix) once it is tagged.
In the meantime, I suggest using bindgen 0.72.1. If you don't want to change
your installed version, you can install it separately:
cargo install bindgen-cli --version 0.72.1 --locked --root /tmp/bindgen-0.72.1
Then pass BINDGEN=/tmp/bindgen-0.72.1/bin/bindgen to your make command.
next prev parent reply other threads:[~2026-11-04 0:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 23:25 drm-rust-next needs a commit from rust-fixes John Hubbard
2026-11-04 0:10 ` Danilo Krummrich [this message]
2026-11-04 2:33 ` John Hubbard
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=DMLZOJTIQ2N6.1WNIKHGVV3U7T@kernel.org \
--to=dakr@kernel.org \
--cc=acourbot@nvidia.com \
--cc=jhubbard@nvidia.com \
--cc=nova-gpu@lists.linux.dev \
--cc=rust-for-linux@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