All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Adverg Ebashinskii" <ebashinskii@mail.ru>
To: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>,
	kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re[6]: Kernel bug tracker
Date: Sun, 05 Sep 2021 13:07:22 +0300	[thread overview]
Message-ID: <1630836442.333321529@f119.i.mail.ru> (raw)
In-Reply-To: <41823.1630683623@turing-police>


[-- Attachment #1.1: Type: text/plain, Size: 573 bytes --]


Hi Valdis,
 
> You might want to read this
 
Thanks for the info it was very interesting to read. My primary intention of getting into the Linux Kernel Development is that I myself used to be a C/Linux developer for years on the user side and pretty well-versed in the Linux user-space API. But the thing is that I have almost zero knowledge of what actually going on under the hood and how to debug and fix complicated problems related to the Kernel itself.  So this is the reason of my interest precisely to core subsystems.
 
--
Regards,
Adverg Ebashinskii
 
 

[-- Attachment #1.2: Type: text/html, Size: 1890 bytes --]

[-- Attachment #2: Type: text/plain, Size: 170 bytes --]

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

      parent reply	other threads:[~2021-09-05 10:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1630220663.155756289@f748.i.mail.ru>
2021-08-29  8:50 ` Kernel bug tracker Anatoly Pugachev
2021-08-29  9:39   ` Re[2]: " Adverg Ebashinskii
2021-08-31  7:09     ` Valdis Klētnieks
     [not found] ` <1630659311.419989149@f519.i.mail.ru>
     [not found]   ` <41823.1630683623@turing-police>
2021-09-05 10:07     ` Adverg Ebashinskii [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=1630836442.333321529@f119.i.mail.ru \
    --to=ebashinskii@mail.ru \
    --cc=kernelnewbies@kernelnewbies.org \
    --cc=valdis.kletnieks@vt.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.