All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Amit Kumar <free.amit.kumar@gmail.com>
Cc: Jules Irenge <jbi.octave@gmail.com>,
	Kernel Newbies <kernelnewbies@kernelnewbies.org>
Subject: Re: My effort to learn Linux kernel development
Date: Fri, 23 Jul 2021 07:54:04 -0400 (EDT)	[thread overview]
Message-ID: <fe27e3c5-f5f3-128a-c9e3-e04a64c1286@crashcourse.ca> (raw)
In-Reply-To: <CAPTh4OtGUr6-FUagroKwQ=-jCp4aPaxy9dyLVbXuzGBzaVYr7A@mail.gmail.com>

On Fri, 23 Jul 2021, Amit Kumar wrote:

... lots of stuff snipped ...

> Thanks for your words. I kindly request your mentorship. So that it
> will be easy for me to make my blog
> (https://freeark1blog.blogspot.com) as a gateway to the Linux kernel
> development.

  i dropped gregkh from this response as i don't think he's interested
in any followup, so here's my thoughts.

  i checked out a couple articles at your blog and i'm not trying to
be harsh, but there's very little useful content there. aside from the
numerous spelling mistakes, the articles are extremely superficial
and, in many cases, are imprecise to the point where it's not clear
what you're even trying to say.

  here's an example:

"Kernel is like the kernel of a nut. It is a bit difficult for an
application program to interact with the kernel directly i.e. it will
be a time consuming task to write an application program with the help
of the kernel only."

  i have no idea what that means, or what point you're trying to get
across, and most of the articles there are like that. if you want to
keep writing, that's great, do whatever you enjoy, but you're being
wildly optimistic if you want to describe your blog as a "gateway to
linux kernel development."

  if i were you, i would do less writing, and way more reading. again,
i'm not trying to discourage you, but you really need to set your
expectations appropriately.

rday

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

  parent reply	other threads:[~2021-07-23 11:54 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-21 14:01 My effort to learn Linux kernel development Amit Kumar
2021-07-22  3:14 ` Amit Kumar
2021-07-22 14:34 ` Jules Irenge
2021-07-22 14:56   ` Robert P. J. Day
2021-07-22 23:24     ` Amit Kumar
2021-07-23  6:43       ` Greg KH
2021-07-23  9:32         ` Amit Kumar
2021-07-23  9:45           ` Greg KH
2021-07-23 11:54           ` Robert P. J. Day [this message]
2021-07-23 14:17             ` Amit Kumar
2021-07-23 14:37               ` Raghuram Jallipalli
2021-07-23 16:15                 ` Connor Kuehl
2021-07-23 16:23                   ` sri vathsa
2021-07-23 10:41       ` Robert P. J. Day
2021-07-23 11:23         ` Amit Kumar
2021-07-25  1:00       ` Aruna Hewapathirane
2021-08-02 14:31         ` Cindy Sue Causey
2021-08-02 17:33           ` Gabriel Moreira
2021-08-10 13:10           ` Aruna Hewapathirane
2021-08-11  9:32             ` Amit Kumar
2021-08-11  9:41               ` sri vathsa
2021-08-11 11:37                 ` Amit Kumar
2021-08-13  1:46                   ` Amit Kumar
2021-08-15 16:28                     ` Amit Kumar
2021-07-24 19:26     ` Constantine Shulyupin
2021-07-24 19:38       ` Robert P. J. Day

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=fe27e3c5-f5f3-128a-c9e3-e04a64c1286@crashcourse.ca \
    --to=rpjday@crashcourse.ca \
    --cc=free.amit.kumar@gmail.com \
    --cc=jbi.octave@gmail.com \
    --cc=kernelnewbies@kernelnewbies.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 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.