rust-for-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Stappers <stappers@stappers.nl>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
	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:35:14 +0200	[thread overview]
Message-ID: <20220928163514.442xdz4eziuoz2fl@gpm.stappers.nl> (raw)
In-Reply-To: <CANiq72nAUKmcBWYqJ0WRHzJbad9L2RrOMP9DY9EYqDD8qSx0RQ@mail.gmail.com>

On Wed, Sep 28, 2022 at 05:24:23PM +0200, Miguel Ojeda wrote:
> On Wed, Sep 28, 2022 at 4:49 PM Geert Stappers 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.

At https://github.com/Rust-for-Linux/linux/pulls/fujita
are two open Merge Requests  (no closed MRs).
 

My original question has been answered, thanks.


Summary of text below:
| } } Should I jump in the swimming pool?
| } Yes, the water temperature is fine
| It looks very cold to me


> >   * 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.
 
README.md at https://github.com/fujita/rust-e1000 hints,
hints me, "this part should be inserted in another source tree".


> >   * 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.

Time will tell which smart[*] questions will be asked.

 
Groeten
Geert Stappers

[*] http://www.catb.org/~esr/faqs/smart-questions.html
-- 
Silence is hard to parse

  reply	other threads:[~2022-09-28 16:35 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 [this message]
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=20220928163514.442xdz4eziuoz2fl@gpm.stappers.nl \
    --to=stappers@stappers.nl \
    --cc=alex.gaynor@gmail.com \
    --cc=miguel.ojeda.sandonis@gmail.com \
    --cc=rust-for-linux@vger.kernel.org \
    --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).