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 17:24:23 +0200 [thread overview]
Message-ID: <CANiq72nAUKmcBWYqJ0WRHzJbad9L2RrOMP9DY9EYqDD8qSx0RQ@mail.gmail.com> (raw)
In-Reply-To: <20220928143120.iavijwru6r3qnhiy@gpm.stappers.nl>
On Wed, Sep 28, 2022 at 4:49 PM Geert Stappers <stappers@stappers.nl> wrote:
>
> Where to look for such merge request?
Tomonori has been sending nice PRs for a while -- you can look them up
using the author filter in GitHub, for instance.
> * git clone a modified version of a modified version of Linux kernel
> * git clone the rust-e1000 at the right place
I would expect the branch to contain whatever is needed, thus you
should only need to clone/fetch/checkout a single branch, i.e. without
having to do merges.
> * build "rust for linux"
> * start qemu with correct parameters
> * find out that existing e1000 driver is NOT in the way
Those are pretty standard steps, though I guess you could prepare a
container or VM image with everything ready if you need it for demo
purposes.
Cheers,
Miguel
next prev parent reply other threads:[~2022-09-28 15:25 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 [this message]
2022-09-28 16:35 ` Geert Stappers
2022-09-28 16:46 ` Miguel Ojeda
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=CANiq72nAUKmcBWYqJ0WRHzJbad9L2RrOMP9DY9EYqDD8qSx0RQ@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).