From: Sebastian Reichel <sebastian.reichel@collabora.co.uk>
To: Colin King <colin.king@canonical.com>
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] power: ab8500_charger: fix spelling mistake: "prechage" -> "precharge"
Date: Mon, 1 May 2017 13:34:49 +0200 [thread overview]
Message-ID: <20170501113449.bxifdqjshgupsf2o@earth> (raw)
In-Reply-To: <20170429215649.11845-1-colin.king@canonical.com>
[-- Attachment #1: Type: text/plain, Size: 279 bytes --]
Hi,
On Sat, Apr 29, 2017 at 10:56:49PM +0100, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> trivial fix to spelling mistake in dev_error message.
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
Thanks, queued.
-- Sebastian
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2017-05-01 11:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-29 21:56 [PATCH] power: ab8500_charger: fix spelling mistake: "prechage" -> "precharge" Colin King
2017-05-01 11:34 ` Sebastian Reichel [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=20170501113449.bxifdqjshgupsf2o@earth \
--to=sebastian.reichel@collabora.co.uk \
--cc=colin.king@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@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