rust-for-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Carlos Carral <carloscarral13@gmail.com>
To: rust-for-linux@vger.kernel.org
Subject: Regarding SCULL driver
Date: Sun, 25 Apr 2021 10:48:22 -0500	[thread overview]
Message-ID: <CAMU0-c+QrurnfVZofHHtQFKPQ_QTpAeoB67LnXnuEBGjrPQByQ@mail.gmail.com> (raw)

Hello, I've been silently  following the RFC and mailing list for a
while now. I'm a newbie kernel hacker and as it happens, I recently
read the Linux Device Drivers book so I have the scull knowledge very
fresh on my mind. Could I try taking on this PR?

             reply	other threads:[~2021-04-25 15:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-25 15:48 Carlos Carral [this message]
     [not found] ` <20210425162804.imic6oehm5kvzbro@gpm.stappers.nl>
     [not found]   ` <CAMU0-cJRJg9m-ARTzTaxVOSugU8_iLzd=to_crv07j3CehC2tg@mail.gmail.com>
2021-04-25 19:27     ` Fwd: Regarding: Regarding SCULL driver Carlos Carral
2021-04-26 22:54 ` 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=CAMU0-c+QrurnfVZofHHtQFKPQ_QTpAeoB67LnXnuEBGjrPQByQ@mail.gmail.com \
    --to=carloscarral13@gmail.com \
    --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).