rust-for-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: Geert Stappers <stappers@stappers.nl>
Cc: Alex Gaynor <alex.gaynor@gmail.com>,
	FUJITA Tomonori <tomo@exabit.dev>,
	rust-for-linux@vger.kernel.org
Subject: Re: Rust e1000 driver (Intel Ethernet adapter)
Date: Wed, 28 Sep 2022 18:46:59 +0200	[thread overview]
Message-ID: <CANiq72kShUNkypRF9sH-EPeE7qV+dKkstNE8YVvVn_U-fKM2_A@mail.gmail.com> (raw)
In-Reply-To: <20220928163514.442xdz4eziuoz2fl@gpm.stappers.nl>

On Wed, Sep 28, 2022 at 6:35 PM Geert Stappers <stappers@stappers.nl> wrote:
>
> My original question has been answered, thanks.

My pleasure!

> README.md at https://github.com/fujita/rust-e1000 hints,
> hints me, "this part should be inserted in another source tree".

I don't see the quote you mention, but from a quick look it seems he
decided to develop the driver side as an out-of-tree module, with the
abstractions in the Linux one.

While that requires to clone both repos, you don't need to move files
between them: compiling the out-of-tree module after the main repo
should work.

Tomonori can probably clarify more...

Cheers,
Miguel

  reply	other threads:[~2022-09-28 16:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-19  1:38 Rust e1000 driver (Intel Ethernet adapter) FUJITA Tomonori
2022-09-19  1:59 ` Alex Gaynor
2022-09-28 14:31   ` Geert Stappers
2022-09-28 15:24     ` Miguel Ojeda
2022-09-28 16:35       ` Geert Stappers
2022-09-28 16:46         ` Miguel Ojeda [this message]
2022-09-29  6:36           ` FUJITA Tomonori
2022-09-29  6:57         ` FUJITA Tomonori
2022-10-23  7:06 ` FUJITA Tomonori

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=CANiq72kShUNkypRF9sH-EPeE7qV+dKkstNE8YVvVn_U-fKM2_A@mail.gmail.com \
    --to=miguel.ojeda.sandonis@gmail.com \
    --cc=alex.gaynor@gmail.com \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=stappers@stappers.nl \
    --cc=tomo@exabit.dev \
    /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).