From: giedrius.statkevicius@gmail.com (Giedrius Statkevicius)
To: kernelnewbies@lists.kernelnewbies.org
Subject: [PATCH] staging: bcm: vendorspecificextn: Fix coding style
Date: Sun, 02 Nov 2014 17:04:31 +0200 [thread overview]
Message-ID: <545647FF.3020205@gmail.com> (raw)
In-Reply-To: <1414939179.13997.YahooMailNeo@web193201.mail.sg3.yahoo.com>
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
next prev parent reply other threads:[~2014-11-02 15:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-02 14:39 [PATCH] staging: bcm: vendorspecificextn: Fix coding style Sunil Shahu
2014-11-02 15:04 ` Giedrius Statkevicius [this message]
2014-11-03 10:45 ` Sudip Mukherjee
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=545647FF.3020205@gmail.com \
--to=giedrius.statkevicius@gmail.com \
--cc=kernelnewbies@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).