From: Aldo Iljazi <mail@aldo.io>
To: dsterba@suse.cz, chris.mason@fusionio.com,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] FS: BTRFS: fixed coding style issues
Date: Tue, 12 Nov 2013 18:57:43 +0200 [thread overview]
Message-ID: <20131112165743.GA12521@elementary> (raw)
In-Reply-To: <20131104151619.GB16999@twin.jikos.cz>
David Sterba wrote:
> On Mon, Nov 04, 2013 at 03:27:38PM +0200, Aldo Iljazi wrote:
> > Fixed three coding style issues. Replaced spaces with tabs.
> >
> > Signed-off-by: Aldo Iljazi <mail@aldo.io>
> > ---
> > fs/btrfs/dev-replace.c | 6 +++---
> > 1 file changed, 3 insertions(+), 3 deletions(-)
> >
> > diff --git a/fs/btrfs/dev-replace.c b/fs/btrfs/dev-replace.c
> > index 9efb94e..b2fe609 100644
> > --- a/fs/btrfs/dev-replace.c
> > +++ b/fs/btrfs/dev-replace.c
> > @@ -377,7 +377,7 @@ int btrfs_dev_replace_start(struct btrfs_root *root,
> > printk_in_rcu(KERN_INFO
> > "btrfs: dev_replace from %s (devid %llu) to %s) started\n",
> > src_device->missing ? "<missing disk>" :
> > - rcu_str_deref(src_device->name),
> > + rcu_str_deref(src_device->name),
>
> What's the change here? I don't think we need to fix whitespace, this
> makes searching in patch history more boring, namely in case where the
> code looks exactly the same before and after the patch.
>
> The style issues should be best fixed when the patch is about to be
> merged, doing it later like this is kind of not welcome, speaking for
> myself. There are lots of opportunities to do real code cleanups.
>
>
> david
Okay thanks.
--
Aldo Iljazi
next prev parent reply other threads:[~2013-11-12 16:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-04 13:27 [PATCH] FS: BTRFS: fixed coding style issues Aldo Iljazi
2013-11-04 15:16 ` David Sterba
2013-11-12 16:57 ` Aldo Iljazi [this message]
2013-11-05 10:28 ` David Sterba
2013-11-05 10:32 ` Aldo Iljazi
2013-11-05 10:36 ` David Sterba
2013-11-05 10:40 ` Aldo Iljazi
2013-11-05 11:36 ` David Sterba
2013-11-05 12:32 ` Aldo Iljazi
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=20131112165743.GA12521@elementary \
--to=mail@aldo.io \
--cc=chris.mason@fusionio.com \
--cc=dsterba@suse.cz \
--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;
as well as URLs for NNTP newsgroup(s).