From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Colin King <colin.king@canonical.com>
Cc: Support Opensource <support.opensource@diasemi.com>,
linux-input@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH][next] Input: da7280: fix spelling mistake "sequemce" -> "sequence"
Date: Mon, 14 Dec 2020 22:59:55 +0000 [thread overview]
Message-ID: <X9fua+GJ12yawoTM@google.com> (raw)
In-Reply-To: <20201214223109.82924-1-colin.king@canonical.com>
On Mon, Dec 14, 2020 at 10:31:09PM +0000, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> There is a spelling mistake in a dev_err message. Fix it.
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
Applied, thank you.
--
Dmitry
WARNING: multiple messages have this Message-ID (diff)
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Colin King <colin.king@canonical.com>
Cc: Support Opensource <support.opensource@diasemi.com>,
linux-input@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH][next] Input: da7280: fix spelling mistake "sequemce" -> "sequence"
Date: Mon, 14 Dec 2020 14:59:55 -0800 [thread overview]
Message-ID: <X9fua+GJ12yawoTM@google.com> (raw)
In-Reply-To: <20201214223109.82924-1-colin.king@canonical.com>
On Mon, Dec 14, 2020 at 10:31:09PM +0000, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> There is a spelling mistake in a dev_err message. Fix it.
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
Applied, thank you.
--
Dmitry
next prev parent reply other threads:[~2020-12-14 22:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 22:31 [PATCH][next] Input: da7280: fix spelling mistake "sequemce" -> "sequence" Colin King
2020-12-14 22:59 ` Dmitry Torokhov [this message]
2020-12-14 22:59 ` Dmitry Torokhov
2020-12-15 10:35 ` Roy Im
2020-12-15 10:35 ` Roy Im
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=X9fua+GJ12yawoTM@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=colin.king@canonical.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=support.opensource@diasemi.com \
/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.