From: Theodore Ts'o <tytso@mit.edu>
To: Nathan Howard <adanhawthorn@gmail.com>
Cc: adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fs: ext4: block_validity.c
Date: Thu, 9 Feb 2017 14:22:06 -0500 [thread overview]
Message-ID: <20170209192206.cdmeowjoyjipm5rs@thunk.org> (raw)
In-Reply-To: <1486666641-15658-1-git-send-email-adanhawthorn@gmail.com>
On Thu, Feb 09, 2017 at 01:57:21PM -0500, Nathan Howard wrote:
> Fixed coding style issues.
Sorry, I only take coding style fixups as part of substantive (bug
fixes, new features, or optimizatoins) changes to the code in question.
If you're trying to do "my first kernel patch", the recommended place
to practice your skills is the Staging tree.
Cheers,
- Ted
prev parent reply other threads:[~2017-02-09 19:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 18:57 [PATCH] fs: ext4: block_validity.c Nathan Howard
2017-02-09 19:22 ` Theodore Ts'o [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=20170209192206.cdmeowjoyjipm5rs@thunk.org \
--to=tytso@mit.edu \
--cc=adanhawthorn@gmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@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