From mboxrd@z Thu Jan  1 00:00:00 1970
From: giedrius.statkevicius@gmail.com (Giedrius Statkevicius)
Date: Sun, 02 Nov 2014 17:04:31 +0200
Subject: [PATCH] staging: bcm: vendorspecificextn: Fix coding style
In-Reply-To: <1414939179.13997.YahooMailNeo@web193201.mail.sg3.yahoo.com>
References: <1414939179.13997.YahooMailNeo@web193201.mail.sg3.yahoo.com>
Message-ID: <545647FF.3020205@gmail.com>
To: kernelnewbies@lists.kernelnewbies.org
List-Id: kernelnewbies.lists.kernelnewbies.org

On 2014.11.02 16:39, Sunil Shahu wrote:
> Hello,
> 
> I was going through kernel source and found out that I can work on staging area for fixes.
Hello, that's ok. Many people start there.

> I have generated a patch for coding style fixes.
> 
> I have few questions about how do submit my patch and to whom.
> 
> 1) Is it ok if I send it directly to Greg Kroah-Hartman <gregkh@linuxfoundation.org>, who seems to be signing off all the patches in that directory as per git log.

Use scripts/get_maintainer.pl. It will tell you where to send your
patch. Always cc a mailing list because kernel development happens in
public. Also, limit your line text to 72 characters in your e-mail
messages.

> 2) What is the standard procedure to submit my patch after I have verified it. Whom do I send it? How do I get it review? How to get it merged in mainline?

There are various ways to test your patch but at least it must not break
the build and also pass checkpatch.pl tests. If not, you should be able
to defend against the errors/warnings/etc. it issues. It is not always
right.

For the other questions: there is helpful documentation about submitting
patches and about how kernel is developed in
Documentation/development-process/ and also there is
Documentation/SubmittingPatches.

For starters many people recommend doing the eudyptula challenge. Check
it out if you haven't heard about it.

Hopefully this will be helpful,
Giedrius