From: David Sterba <dsterba@suse.cz>
To: Kevin Mulvey <kevin@kevinmulvey.net>
Cc: Chris Mason <clm@fb.com>, Josef Bacik <jbacik@fb.com>,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
Kevin Mulvey <kmulvey@linux.com>
Subject: Re: [PATCH] fix spacing in btrfs/inode.c
Date: Thu, 12 Feb 2015 10:43:17 +0100 [thread overview]
Message-ID: <20150212094317.GO28877@suse.cz> (raw)
In-Reply-To: <1423707442-9485-1-git-send-email-kmulvey@linux.com>
On Wed, Feb 11, 2015 at 09:17:22PM -0500, Kevin Mulvey wrote:
> This is a patch to inode.c that fixes some spacing errors found by checkpatch.pl
https://btrfs.wiki.kernel.org/index.php/Project_ideas#Cleanup_projects
"Please note that pure whitespace and style reformatting changes are not
really necessary at this phase of development. They get fixed along
regular changes. Possibly once upon in a while a patch that fixes many
if not all whitespace errors could work, but otherwise it's considered a
noise."
prev parent reply other threads:[~2015-02-12 9:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-12 2:17 [PATCH] fix spacing in btrfs/inode.c Kevin Mulvey
2015-02-12 9:43 ` David Sterba [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=20150212094317.GO28877@suse.cz \
--to=dsterba@suse.cz \
--cc=clm@fb.com \
--cc=jbacik@fb.com \
--cc=kevin@kevinmulvey.net \
--cc=kmulvey@linux.com \
--cc=linux-btrfs@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