From: Wei Liu <wei.liu@kernel.org>
To: 李弘宇 <lihongyu1999@bupt.edu.cn>
Cc: rust-for-linux <rust-for-linux@vger.kernel.org>,
Wei Liu <wei.liu@kernel.org>
Subject: Re: Which linux kernel version should I choose?
Date: Mon, 3 Jan 2022 11:22:57 +0000 [thread overview]
Message-ID: <20220103112257.mvz25qghrnsapicw@liuwe-devbox-debian-v2> (raw)
In-Reply-To: <20220103112146.pt32tktmjdlb7p3o@liuwe-devbox-debian-v2>
On Mon, Jan 03, 2022 at 11:21:46AM +0000, Wei Liu wrote:
> Hi Hongyu,
>
> On Mon, Jan 03, 2022 at 06:19:10PM +0800, 李弘宇 wrote:
> > Hi, I am interested in the rust for Linux project and want to learn
> > about it. But I have encountered some problems with the Linux kernel
> > version.
> >
> > I want to apply the patchset v2 given in the mail list. I found that
> > the patchset v1 can be applied to Linux kernel v5.13. However, I do
> > not find the correct Linux kernel version for the rust patchset v2.
> > Where can I find this information?
> >
> > Meanwhile, I wonder whether I can generate a patchset by myself so
> > that I can apply it to a specific kernel version I want. I tried to
> > google this but did not find anything related.
> >
>
> You can perhaps start by following the instructions on Github.
>
> See https://github.com/Rust-for-Linux/linux/blob/rust/README.md.
>
> Thanks,
> Wei.
>
> > I want to join the Zulip group. My email address is
> > lihongyu@bupt.edu.cn.
BTW your email here should be lihongyu1999@bupt.edu.cn, right? That's
the address in the From: field of your email.
Thanks,
Wei.
> >
> > Thanks.
next prev parent reply other threads:[~2022-01-03 11:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-03 10:19 Which linux kernel version should I choose? 李弘宇
2022-01-03 11:21 ` Wei Liu
2022-01-03 11:22 ` Wei Liu [this message]
[not found] ` <61d51c88.1c69fb81.3b0da.ae02SMTPIN_ADDED_BROKEN@mx.google.com>
2022-01-05 13:45 ` Wei Liu
2022-01-03 16:20 ` 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=20220103112257.mvz25qghrnsapicw@liuwe-devbox-debian-v2 \
--to=wei.liu@kernel.org \
--cc=lihongyu1999@bupt.edu.cn \
--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