linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anand Jain <Anand.Jain@oracle.com>
To: Josh Marshall <joshua.r.marshall.1991@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: ran cppcheck and going to make cosmetic changes--where do I submit code?
Date: Fri, 04 May 2012 21:14:05 +0800	[thread overview]
Message-ID: <4FA3D61D.50703@oracle.com> (raw)
In-Reply-To: <4FA282D7.9000203@gmail.com>



> where do I submit the code when I'm done?
>
> P.S. This is my first kernel project, so I'm going to need some direction.

  wiki page 'Writing patch for btrfs'  has this info
  http://btrfs.ipv5.de/index.php?title=Writing_patch_for_btrfs

good luck.

-Anand

      parent reply	other threads:[~2012-05-04 13:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-03 13:06 ran cppcheck and going to make cosmetic changes--where do I submit code? Josh Marshall
2012-05-03 13:20 ` Hubert Kario
2012-05-04 13:14 ` Anand Jain [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=4FA3D61D.50703@oracle.com \
    --to=anand.jain@oracle.com \
    --cc=joshua.r.marshall.1991@gmail.com \
    --cc=linux-btrfs@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 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).