From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: Ruben Safir <ruben@mrbrklyn.com>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: New text
Date: Thu, 20 Feb 2020 15:12:17 -0500 [thread overview]
Message-ID: <12972.1582229537@turing-police> (raw)
In-Reply-To: <49985cce-f875-a3ec-8627-757ed720fc38@mrbrklyn.com>
[-- Attachment #1.1: Type: text/plain, Size: 665 bytes --]
On Wed, 19 Feb 2020 18:17:36 -0500, Ruben Safir said:
> > 1) Start wading through the git log until you find the commit that
> > changed the API. In either that commit, or a commit in the same series,
> > whoever changed the API
>
> I don't think that will be a useful way to learn to code the kernel.
That was addressing the specific case of "I need to update an out of tree
driver to a recent kernel".
And I didn't say the kernel is impossible to learn - only that there's no
special consideration given in-tree to beginning kernel hackers. If you don't
already understand topics like locking and caching and file systems, you need
to learn those elsewhere.
[-- Attachment #1.2: Type: application/pgp-signature, Size: 832 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2020-02-20 20:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 15:54 New text Ruben Safir
2020-02-19 21:36 ` Valdis Klētnieks
2020-02-19 23:17 ` Ruben Safir
2020-02-20 20:12 ` Valdis Klētnieks [this message]
2020-02-20 21:06 ` Ruben Safir
2020-02-19 23:43 ` Robert P. J. Day
2020-02-20 1:55 ` Ruben Safir
2020-02-23 3:51 ` Aruna Hewapathirane
2020-03-15 11:10 ` Rishi Agrawal
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=12972.1582229537@turing-police \
--to=valdis.kletnieks@vt.edu \
--cc=kernelnewbies@kernelnewbies.org \
--cc=ruben@mrbrklyn.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).