public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: SIMRAN SINGHAL <singhalsimran0@gmail.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 6/9] staging: rtl8192u: Fixing coding style issues
Date: Wed, 15 Feb 2017 01:23:32 -0800	[thread overview]
Message-ID: <1487150612.6214.48.camel@perches.com> (raw)
In-Reply-To: <CALrZqyPyJ9Z5N91G073hAEr=YTD5BvRUVCikbBh1kxXiq5dx+g@mail.gmail.com>

On Wed, 2017-02-15 at 13:48 +0530, SIMRAN SINGHAL wrote:
> Joe, I am new to Linux kernel and just have basic knowledge of
>  C and C++.
> For doing more than checkpatches I need to explore Linux kernel more,
> so please suggest me some tasks that help me in exploring
> Linux kernel, which helps me in building the better understanding of codes,
> which I am finding difficult to understand so that I can do more than
> just checkpatch.

Linux kernel isn't a great project to learn c/c++ as
it is a relatively old, complex project without a lo
of obvious defects.

see: http://kernelnewbies.org

Make sure you read the kernel newbies lists and the
kernel process help files in Documentation/process/.

In the drivers/staging directory tree are many TODO
files.  Read some of them.

List of kernel related bugs to fix:
https://bugzilla.kernel.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=VERIFIED&bug_status=DEFERRED&bug_status=NEEDINFO&bugidtype=include&chfieldto=Now&cmdtype=doit&emailassigned_to1=1&emailassigned_to2=1&emailcc2=1&emailreporter2=1&emailtype1=substring&emailtype2=substring&field0-0-0=noop&kernel_version_type=allwordssubstr&long_desc_type=substring&order=Reuse%20same%20sort%20as%20last%20time&query_format=advanced&regression=both&short_desc_type=allwordssubstr&type0-0-0=noop

  reply	other threads:[~2017-02-15  9:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-14 20:14 [PATCH v2 6/9] staging: rtl8192u: Fixing coding style issues simran singhal
2017-02-14 20:23 ` Joe Perches
2017-02-15  3:22   ` SIMRAN SINGHAL
2017-02-15  3:31     ` Joe Perches
2017-02-15  8:18       ` SIMRAN SINGHAL
2017-02-15  9:23         ` Joe Perches [this message]
2017-02-16 18:32         ` Greg KH
2017-02-16 19:08           ` SIMRAN SINGHAL

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=1487150612.6214.48.camel@perches.com \
    --to=joe@perches.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=singhalsimran0@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