All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shyam Saini <mayhs11saini@gmail.com>
To: Daniel Baluta <daniel.baluta@gmail.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	Andrew Lunn <andrew@lunn.ch>
Subject: Re: How to submit potential patch in linux kernel
Date: Fri, 30 Sep 2016 06:08:08 +0530	[thread overview]
Message-ID: <1475195888.9322.5.camel@gmail.com> (raw)
In-Reply-To: <CAEnQRZCF8h7+feuDm4Z-HF5fZQ88yiKisg7u0eAEVE27L35y3w@mail.gmail.com>

On Thu, 2016-09-29 at 13:15 +0300, Daniel Baluta wrote:
> Hi Shyam,
> 
> On Thu, Sep 29, 2016 at 1:02 PM, Andrew Lunn <andrew@lunn.ch> wrote:
> > 
> > On Thu, Sep 29, 2016 at 04:32:29AM +0530, Shyam Saini wrote:
> > > 
> > > Hi everyone,
> > > 
> > > I'm Shyam, final year undergraduate student. I wanted to know how
> > > one can
> > > submit potential linux kernel patch in networking subsystem.
> > Documentation/SubmittingPatches is a good starting point.
> > 
> > Then post a patch and we will help you learn the rest of the
> > process.
> 
> You can have a look at https://kernelnewbies.org/FirstKernelPatch.
> There is also this presentation from Greg:
> https://www.youtube.com/watch?v=LLBrBBImJt4
> 
> thanks,
> Daniel.


Thanks for your reply. But I already know how to submit patches. I've
submitted some trivial kernel patches. But Now, I want to submit some
potential or good patches. 
So, I wanted to know how can I move to that direction? 

Thanks, 
Shyam

      reply	other threads:[~2016-09-30  0:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-28 23:02 How to submit potential patch in linux kernel Shyam Saini
2016-09-29 10:02 ` Andrew Lunn
2016-09-29 10:15   ` Daniel Baluta
2016-09-30  0:38     ` Shyam Saini [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=1475195888.9322.5.camel@gmail.com \
    --to=mayhs11saini@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=daniel.baluta@gmail.com \
    --cc=netdev@vger.kernel.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.