From: Douglas Su <d0u9.su@gmail.com>
To: "rust-for-linux@vger.kernel.org" <rust-for-linux@vger.kernel.org>
Subject: How rust subsystem handles long symbols of rust function
Date: Fri, 28 May 2021 13:48:00 +0800 [thread overview]
Message-ID: <CABDqbH2Zhhwh=XL7p4sxVKxFjnK4xxO_xT5oac9ZyoHe3xkU8A@mail.gmail.com> (raw)
I am recently playing around with the Rust subsystem in Kernel, and
notice that the symbols generated from Rust relevant functions are
longer than normal C counterparts.
If I am not wrong, Kernel imposes symbol length restriction on
functions and variables. So, what efforts have been made to make
Rust's symbols compatible with Kernel's rule?
Sincerely
Douglas
next reply other threads:[~2021-05-28 5:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-28 5:48 Douglas Su [this message]
2021-05-28 9:03 ` How rust subsystem handles long symbols of rust function Greg KH
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='CABDqbH2Zhhwh=XL7p4sxVKxFjnK4xxO_xT5oac9ZyoHe3xkU8A@mail.gmail.com' \
--to=d0u9.su@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).