LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] regulator: Minor regulator documentation fixes.
Date: Thu, 19 Aug 2021 12:43:54 +0100	[thread overview]
Message-ID: <20210819114354.GL4177@sirena.org.uk> (raw)
In-Reply-To: <67f6596f54fd2ea168d71d0747ea4a521dda5384.camel@fi.rohmeurope.com>

[-- Attachment #1: Type: text/plain, Size: 829 bytes --]

On Thu, Aug 19, 2021 at 08:06:48AM +0300, Matti Vaittinen wrote:

> I was thinking of that. I thought that it made less of a hassle with
> single patch. After all, both changes were doc updates - and I didn't
> think the typofix warranted backport or a Fixed tag.

> Could you please educate me & explain why would you have preferred two
> patches? (I see you any ways applied this so I guess there's no need to
> split & resend - thanks).

It's two changes that don't overlap in any way.  Part of the reason for
splitting patches up is that it reduces the cogantive load checking that
the patch actually does the thing described in the changelog, with two
changes in one patch you need to hold two things in your head at once.
The more trivial the patch the bigger the extra effort relative to what
they'd have taken otherwise.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2021-08-19 11:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-18  4:18 Matti Vaittinen
2021-08-18 12:17 ` Mark Brown
2021-08-19  5:06   ` Matti Vaittinen
2021-08-19 11:43     ` Mark Brown [this message]
2021-08-19 11:55       ` Vaittinen, Matti
2021-08-18 16:26 ` Mark Brown

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=20210819114354.GL4177@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matti.vaittinen@fi.rohmeurope.com \
    --subject='Re: [PATCH] regulator: Minor regulator documentation fixes.' \
    /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

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).