All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mason <slash.tmp@free.fr>
To: Mans Rullgard <mans@mansr.com>
Cc: Sebastian Frias <sf84@laposte.net>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Magnus Damm <damm@opensource.se>,
	linux-serial@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] use callbacks to access UART_DLL/UART_DLM
Date: Thu, 17 Dec 2015 20:14:13 +0100	[thread overview]
Message-ID: <56730985.1080609@free.fr> (raw)
In-Reply-To: <yw1xbn9pc5h8.fsf@unicorn.mansr.com>

On 17/12/2015 19:09, Måns Rullgård wrote:

> It could well be that your patch results in a clearer final version, but
> the diff is harder to parse when unchanged lines have moved around.

When all other things are equal, is the priority

1) making the patch as clear as possible?
2) making the resulting code as clear as possible?

On a related note, I remember spotting a problem in a phy driver
commit, and was told (by you) that I should split my fix in 3 (!!)
patches. I'm sorry, but that's a double standard, why would the
initial committer be given the leeway to post a single patch,
but someone willing to clean up his mess should work harder?

End result: I left the bug in there.

Regards.

  reply	other threads:[~2015-12-17 19:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-17 15:45 [PATCH] use callbacks to access UART_DLL/UART_DLM Sebastian Frias
2015-12-17 16:02 ` Måns Rullgård
2015-12-17 18:07   ` Sebastian Frias
2015-12-17 18:09     ` Måns Rullgård
2015-12-17 19:14       ` Mason [this message]
2015-12-18 10:46     ` [PATCH v2] " Sebastian Frias
2015-12-18 16:06       ` Peter Hurley
2015-12-18 16:27         ` Sebastian Frias
2015-12-18 16:34           ` Peter Hurley
2015-12-18 16:35             ` Sebastian Frias
2015-12-18 16:40         ` [PATCH v3] " Sebastian Frias
2015-12-18 16:42           ` Peter Hurley

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=56730985.1080609@free.fr \
    --to=slash.tmp@free.fr \
    --cc=damm@opensource.se \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=mans@mansr.com \
    --cc=sf84@laposte.net \
    /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.