mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: gregkh <gregkh@linuxfoundation.org>
To: sanjeev sharma <sanjeevsharmaengg@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Open-ended task In kernel
Date: Tue, 29 Jul 2014 08:14:51 -0700	[thread overview]
Message-ID: <20140729151451.GA9080@kroah.com> (raw)
In-Reply-To: <CAGUYZuQxJtjNKfvpEY_6GR1SxZCcbmwv5p0Lpu5jx7CgC5os9Q@mail.gmail.com>

On Tue, Jul 29, 2014 at 12:46:46PM +0530, sanjeev sharma wrote:
> Hello All,
> 
> I have started recently in contributing into Linux kernel and submitted patches
> in staging directory and now I want to do outside staging directory specially
> in main kernel and driver part.Do we have anything in Linux kernel i.e some
> specific areas which I can looked upon.I think we should have some list of
> open-point where people can contribute.
> 
> If anyone has some information,please share on mailing list so that I can focus
> myself in correct direction.

Yes, I know lots of "open ended" tasks in the kernel.

But just because I, or someone else, writes them down doesn't mean that
you will want to do them, or be sucessful at them.

My suggestion always is, "Find something that bothers you, fix it, and
go from there."  And if you can't find a problem with the kernel on your
machine, then you really aren't looking hard enough.

Best of luck,

greg k-h

  parent reply	other threads:[~2014-07-29 15:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAGUYZuQxJtjNKfvpEY_6GR1SxZCcbmwv5p0Lpu5jx7CgC5os9Q@mail.gmail.com>
     [not found] ` <CAGUYZuTG=XtX8-wj33dRaQGyzad0HQEmzr0RfPkX_Kme2voLzA@mail.gmail.com>
2014-07-29  7:21   ` Fwd: " sanjeev sharma
2014-07-29 15:14 ` gregkh [this message]
2014-07-30  5:18   ` sanjeev sharma
2014-07-30  7:13     ` Abhay Sachan

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=20140729151451.GA9080@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sanjeevsharmaengg@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

all inboxes | Powered by JetHome®