From: Amy Parker <apark0006@student.cerritos.edu>
To: Alex Gaynor <alex.gaynor@gmail.com>
Cc: linux-newbie@vger.kernel.org,
rust-for-linux <rust-for-linux@vger.kernel.org>
Subject: Re: Assisting with kernel Rust development
Date: Tue, 6 Jul 2021 10:39:56 -0700 [thread overview]
Message-ID: <CAPOgqxGUYzqxqO83fMY04uL=fUr_OGm3X+s-fBSCQtU1x_ur_Q@mail.gmail.com> (raw)
In-Reply-To: <CAFRnB2WMuOjP0S5vvCa9w1Wi67K+3XcBsZ+QxxQ2gvo4-2mOEw@mail.gmail.com>
On Tue, Jul 6, 2021 at 10:23 AM Alex Gaynor <alex.gaynor@gmail.com> wrote:
>
> Hi Amy,
>
> Glad to hear you're interested! We've got a whole bunch of open bugs
> on https://github.com/Rust-for-Linux/linux/issues, so that's always a
> starting point for looking for things to work on.
>
> Cheers,
> Alex
>
> On Tue, Jul 6, 2021 at 1:19 PM Amy Parker
> <apark0006@student.cerritos.edu> wrote:
> >
> > Hello!
> >
> > My name is Amy Parker. You may have seen me on the kernel forums before under my previous email address <enbyamy@gmail.com>.
> >
> > It's been a while since I've attempted to contribute to the kernel, so I figured I'd post here. My previous attempt had been under Matthew Wilcox's direction to modify the DAX driver for NVDIMMs to use XA_ZERO_ENTRY to represent a zero page instead of DAX_ZERO_PAGE (allowing us to save a constant) - but this failed since the ascending values of other flags conflicted with the value presented by XA_ZERO_ENTRY.
> >
> > I saw the recent patch sequence adding Rust support to the kernel. As a Rust developer, I figured I could get back into kernel development because of this, and was wondering how I could help. Are there any active objectives that need work?
> >
>
>
> --
> All that is necessary for evil to succeed is for good people to do nothing.
Okay, I will!
Thank you.
-amyip
prev parent reply other threads:[~2021-07-06 17:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-06 17:19 Assisting with kernel Rust development Amy Parker
2021-07-06 17:23 ` Alex Gaynor
2021-07-06 17:39 ` Amy Parker [this message]
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='CAPOgqxGUYzqxqO83fMY04uL=fUr_OGm3X+s-fBSCQtU1x_ur_Q@mail.gmail.com' \
--to=apark0006@student.cerritos.edu \
--cc=alex.gaynor@gmail.com \
--cc=linux-newbie@vger.kernel.org \
--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).