From: Bernd Petrovitsch <bernd@petrovitsch.priv.at>
To: Raphael <locknaraffi@gmail.com>, kernelnewbies@kernelnewbies.org
Subject: Re: How can I compile a rc kernel myself?
Date: Sat, 21 Mar 2020 11:23:55 +0100 [thread overview]
Message-ID: <6f12a330-1879-ad97-f349-f88a06f8d424@petrovitsch.priv.at> (raw)
In-Reply-To: <20200321101205.rr4pzwgubhznqevm@lockna>
Hi!
On 21/03/2020 11:12, Raphael wrote:
[...]
> I was wondering how I can compile a rc kernel, since rc is only a patch and I have to apply this patch to a stable kernel first.
Easiest is to `git clone` an appropriate tree + tag (sry, I don't
have a link) - everything is in some git-repo;-)
MfG,
Bernd
--
Bernd Petrovitsch Email : bernd@petrovitsch.priv.at
LUGA : http://www.luga.at
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
prev parent reply other threads:[~2020-03-21 10:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-21 10:12 How can I compile a rc kernel myself? Raphael
2020-03-21 10:23 ` Bernd Petrovitsch [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=6f12a330-1879-ad97-f349-f88a06f8d424@petrovitsch.priv.at \
--to=bernd@petrovitsch.priv.at \
--cc=kernelnewbies@kernelnewbies.org \
--cc=locknaraffi@gmail.com \
/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).