From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: Finn Behrens <me@kloenk.de>
Cc: rust-for-linux@vger.kernel.org
Subject: Re: module as seperate crate
Date: Sun, 29 Nov 2020 18:51:24 +0100 [thread overview]
Message-ID: <CANiq72kKthjwUvBpHHPbhFsE555DriFVTtm2ziFTjwnPH_aA=A@mail.gmail.com> (raw)
In-Reply-To: <aa2ff401-d552-fd46-b2c3-2058af8226c3@kloenk.de>
On Sun, Nov 29, 2020 at 6:38 PM Finn Behrens <me@kloenk.de> wrote:
>
> What is the reason for module being an extra crate? I would have to run
> some generic setup code for kernel/printk, but as the module macro being
> from an extra crate, I cannot easily run some code there. Should we
> maybe move module into the kernel crate, to make this easier?
It is because it is a proc macro. Otherwise, if Rust supported proc
macros in the same crate, we could do it, yeah.
Cheers,
Miguel
next prev parent reply other threads:[~2020-11-29 17:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-29 17:36 module as seperate crate Finn Behrens
2020-11-29 17:51 ` Miguel Ojeda [this message]
2020-11-29 17:54 ` Finn Behrens
[not found] ` <d417fec0-c5c6-edda-796e-a861f5518eed@kloenk.de>
[not found] ` <CANiq72negqN+2eOjieYW1Zas1ays3t3W-+wZisXjF9q=kob3yw@mail.gmail.com>
2020-11-29 18:30 ` Finn Behrens
2020-12-09 23:20 ` Miguel Ojeda
2020-12-12 23:48 ` Wedson Almeida Filho
2020-12-13 1:00 ` Miguel Ojeda
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='CANiq72kKthjwUvBpHHPbhFsE555DriFVTtm2ziFTjwnPH_aA=A@mail.gmail.com' \
--to=miguel.ojeda.sandonis@gmail.com \
--cc=me@kloenk.de \
--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).