rust-for-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Manas <manas18244@iiitd.ac.in>
To: Geert Stappers <stappers@stappers.nl>
Cc: rust-for-linux@vger.kernel.org
Subject: Re: Missing RUST_EXAMPLE option in linux-next-20210331
Date: Thu, 1 Apr 2021 17:29:05 +0530	[thread overview]
Message-ID: <20210401115905.7ttbyfv4m5haskwr@nitro-5> (raw)
In-Reply-To: <20210401113110.jihwi65ayan2ngi4@gpm.stappers.nl>

On Thu, Apr 01, 2021 at 01:31:10PM +0200, Geert Stappers wrote:
> On Thu, Apr 01, 2021 at 11:48:40AM +0530, Manas wrote:
> > I am working on a device driver in rust in linux-next as an academic
> > project. I used the following command to create .config:
> > 
> > $ make LLVM=1 menuconfig
> > 
> > But, sometimes the RUST_EXAMPLE option is not visible in menuconfig
> > (under /Device Drivers/Character devices/). It seemingly happens at
> > random that this option disappears, despite having a working rust 
> > nightly environment (and other dependencies).
> > 
> > My rust nightly version is 2021-02-20-x86_64-unknown-linux-gnu, with 
> > rustc 1.52.0-nightly.
> > 
> > Can someone point me to why is this happening?
> 
> Time will answer that question.
> 
> 
> Thing I would like to known if this "randomness" happens
> in the very same git branch. Does it? [Yes/No]
> 
I am not sure. I haven't checked with other branches.

-- 
Manas
CSAM Undergraduate | 2022
IIIT-Delhi, India

  reply	other threads:[~2021-04-01 17:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-01  6:18 Missing RUST_EXAMPLE option in linux-next-20210331 Manas
2021-04-01 11:31 ` Geert Stappers
2021-04-01 11:59   ` Manas [this message]
2021-04-01 18:38     ` Geert Stappers
2021-04-01 15:07 ` Miguel Ojeda
2021-04-02  0:35   ` Manas
2021-04-02  1:19     ` Miguel Ojeda
2021-04-02  1:47       ` Manas

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=20210401115905.7ttbyfv4m5haskwr@nitro-5 \
    --to=manas18244@iiitd.ac.in \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=stappers@stappers.nl \
    /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).