From: Theodore Ts'o <tytso@mit.edu>
To: Jiri Slaby <jslaby@suse.cz>
Cc: Jan Mrazek <email@honzamrazek.cz>,
linux-ext4@vger.kernel.org, trivial@kernel.org,
Jiri Slaby <gep@mail.muni.cz>
Subject: Re: [PATCH] Fix of coding style
Date: Tue, 20 Jan 2015 12:27:09 -0500 [thread overview]
Message-ID: <20150120172709.GB24217@thunk.org> (raw)
In-Reply-To: <54BE4C0B.3030703@suse.cz>
On Tue, Jan 20, 2015 at 01:37:31PM +0100, Jiri Slaby wrote:
> On 01/20/2015, 12:59 PM, Jan Mrazek wrote:
> > - init_timer changed to setup_timer
> > - multiline strings changed to single line (so it can be greped)
> > - other small conding style changes
> >
> > Signed-off-by: Jan Mrazek <email@honzamrazek.cz>
>
> Note that one hunk does not apply cleanly here:
> Hunk #35 succeeded at 3581 with fuzz 1 (offset 16 lines).
>
> What tree did you use as a base? Care to rebase?
>
> Reviewed-by: Jiri Slaby <jslaby@suse.cz>
>
> (There is a nit: leaving up to the maintainers if they insist on
> separating the setup_timer change or not :).)
Yes, please separate it out; in general I'm not terribly excited about
these sorts of massive cleanup patches, because it breaks patches that
other people send me. (I'll also note that many of the multi-line
separations happened people running checkpatch sent me cleanup
patches; so the fact that I'm now getting a cleanup patch to reverse
this also predisposes me to not be very receptive to these sorts of
cleanups. I will generally ask developers to send me checkpatch clean
patches, but I'm less enthusiastic about cleanup patches for their own
sake.)
That being said, the setup_timer change is small, and less disruptive,
so separating that out is good because I will likely accept the
setup_timer change, but probably not the multi-line string change,
since regardless of what you base it against, there is a very good
chance it won't apply against the ext4 development tree --- and if it
does, it will likely break other patches that people send me.
Cheers,
- Ted
prev parent reply other threads:[~2015-01-20 17:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-20 11:59 [PATCH] Fix of coding style Jan Mrazek
2015-01-20 12:37 ` Jiri Slaby
2015-01-20 17:27 ` 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=20150120172709.GB24217@thunk.org \
--to=tytso@mit.edu \
--cc=email@honzamrazek.cz \
--cc=gep@mail.muni.cz \
--cc=jslaby@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=trivial@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.