From: Mark Brown <broonie@kernel.org>
To: Michael Klein <michael@fossekall.de>
Cc: Andrei Stefanescu <andrei.stefanescu@microchip.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Support Opensource <support.opensource@diasemi.com>,
Lee Jones <lee.jones@linaro.org>,
linux-kernel@vger.kernel.org, trivial@kernel.org
Subject: Re: [PATCH v2 1/3] Documentation: mcp16502-regulator: fix spelling mistake
Date: Fri, 27 Nov 2020 13:48:09 +0000 [thread overview]
Message-ID: <20201127134809.GB4845@sirena.org.uk> (raw)
In-Reply-To: <20201127125202.23917-1-michael@fossekall.de>
[-- Attachment #1: Type: text/plain, Size: 771 bytes --]
On Fri, Nov 27, 2020 at 01:52:00PM +0100, Michael Klein wrote:
> Signed-off-by: Michael Klein <michael@fossekall.de>
> ---
> No changes in v2
Please do not submit new versions of already applied patches, please
submit incremental updates to the existing code. Modifying existing
commits creates problems for other users building on top of those
commits so it's best practice to only change pubished git commits if
absolutely essential.
Please submit patches using subject lines reflecting the style for the
subsystem, this makes it easier for people to identify relevant patches.
Look at what existing commits in the area you're changing are doing and
make sure your subject lines visually resemble what they're doing.
There's no need to resubmit to fix this alone.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-11-27 13:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-24 18:37 [PATCH 0/2] Fix spelling of "regulator" Michael Klein
2020-11-24 18:37 ` [PATCH 1/2] Documentation: mcp16502-regulator: fix spelling mistake Michael Klein
2020-11-24 18:37 ` [PATCH 2/2] mfd: fix spelling mistakes Michael Klein
2020-11-27 9:31 ` Lee Jones
2020-11-27 12:52 ` [PATCH v2 1/3] Documentation: mcp16502-regulator: fix spelling mistake Michael Klein
2020-11-27 12:52 ` [PATCH v2 2/3] mfd: si476x-core.h: fix "regulator" spelling in comment Michael Klein
2020-11-27 13:19 ` Lee Jones
2020-11-27 12:52 ` [PATCH v2 3/3] mfd: da9055: fix "REGULATOR" spelling in register content macro Michael Klein
2020-11-27 13:07 ` Adam Thomson
2020-11-27 13:18 ` Lee Jones
2020-11-27 13:48 ` Mark Brown [this message]
2020-11-25 12:00 ` [PATCH 0/2] Fix spelling of "regulator" 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=20201127134809.GB4845@sirena.org.uk \
--to=broonie@kernel.org \
--cc=andrei.stefanescu@microchip.com \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@fossekall.de \
--cc=robh+dt@kernel.org \
--cc=support.opensource@diasemi.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®