From: Linus Torvalds <torvalds@linux-foundation.org>
To: Andrew Morton <akpm@linux-foundation.org>,
Uros Bizjak <ubizjak@gmail.com>
Cc: linux-mm@kvack.org, mm-commits@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] MM updates for 6.14-rc1
Date: Sat, 25 Jan 2025 14:09:16 -0800 [thread overview]
Message-ID: <CAHk-=whddBhfi5DUi370W3pYs+z3r2E7KYuHjwR=a1eRig5Gxg@mail.gmail.com> (raw)
In-Reply-To: <20250124162248.60104eec848619a187242392@linux-foundation.org>
On Fri, 24 Jan 2025 at 16:22, Andrew Morton <akpm@linux-foundation.org> wrote:
>
> Linus, please merge the MM updates for the 6.14 development cycle,
This does not build at all for me.
I get
./arch/x86/include/asm/current.h:49:9: error: call to undeclared
function '__typeof_unqual__'; ISO C99 and later do not support
implicit function declarations [-Wimplicit-function-declaration]
when running the Rust 'bindgen', and what seems to be going on is that
my version of *gcc* does support __typeof_unqual__, so I end up with
CONFIG_CC_HAS_TYPEOF_UNQUAL=y
in my kernel config, but I think that 'bindgen' that generates the
Rust bindings is based on LLVM, and clearly does not understand
__typeof_unqual__.
I have bindgen 0.69.5 (plain F40 install), in case somebody wants to test.
Apparently few people test linux-next with Rust enabled, and the
reports that I find on lkml were ignored.
I do see reports of this failure on lkml from mid-December, so it's
not like I'm the first person ever to see this.
Anyway, pulled and then unpulled again.
Linus
next prev parent reply other threads:[~2025-01-25 22:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-25 0:22 Andrew Morton
2025-01-25 22:09 ` Linus Torvalds [this message]
2025-01-26 5:00 ` Andrew Morton
2025-01-26 7:34 ` Linus Torvalds
2025-01-26 8:27 ` Stephen Rothwell
2025-01-26 12:10 ` Uros Bizjak
2025-01-26 9:57 ` Uros Bizjak
2025-01-26 17:21 ` Uros Bizjak
2025-01-26 18:29 ` Linus Torvalds
2025-01-26 19:46 ` Uros Bizjak
2025-01-26 20:06 ` Uros Bizjak
2025-01-26 21:59 ` Linus Torvalds
2025-01-26 23:27 ` Uros Bizjak
2025-01-27 0:08 ` Linus Torvalds
2025-01-27 7:29 ` Uros Bizjak
2025-01-26 20:28 ` Miguel Ojeda
2025-01-26 21:19 ` Matthew Wilcox
2025-01-26 21:35 ` Miguel Ojeda
2025-01-26 20:58 ` Miguel Ojeda
2025-01-29 20:10 ` 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='CAHk-=whddBhfi5DUi370W3pYs+z3r2E7KYuHjwR=a1eRig5Gxg@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mm-commits@vger.kernel.org \
--cc=ubizjak@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