From: "Tomasz Pakuła" <tomasz.pakula.oficjalny@gmail.com>
To: Colin Ian King <colin.i.king@gmail.com>,
Oleg Makarenko <oleg@makarenk.ooo>,
Jiri Kosina <jikos@kernel.org>,
Benjamin Tissoires <bentiss@kernel.org>,
linux-input@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][next] HID: hid-universal-pidff: Fix spelling mistake "sucessfully" -> "successfully"
Date: Wed, 12 Feb 2025 14:30:59 +0100 [thread overview]
Message-ID: <067382bbfaa4bf9729a8d8ba1a7afb387ba04bd4.camel@gmail.com> (raw)
In-Reply-To: <20250212122347.495701-1-colin.i.king@gmail.com>
On Wed, 2025-02-12 at 12:23 +0000, Colin Ian King wrote:
> There is a spelling mistake in a hid_info message. Fix it.
>
> Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
> ---
> drivers/hid/hid-universal-pidff.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/hid/hid-universal-pidff.c b/drivers/hid/hid-universal-pidff.c
> index 5b89ec7b5c26..001a0f5efb9d 100644
> --- a/drivers/hid/hid-universal-pidff.c
> +++ b/drivers/hid/hid-universal-pidff.c
> @@ -104,7 +104,7 @@ static int universal_pidff_probe(struct hid_device *hdev,
> goto err;
> }
>
> - hid_info(hdev, "Universal pidff driver loaded sucessfully!");
> + hid_info(hdev, "Universal pidff driver loaded successfully!");
>
> return 0;
> err:
Huh, I actually "fixed" that word recently but only added one missing
's'. It's a tricky word for sure :)
Applies cleanly on top of hid.git#for-6.15/pidff
Acked-by: Tomasz Pakuła <tomasz.pakula.oficjalny@gmail.com>
next prev parent reply other threads:[~2025-02-12 13:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-12 12:23 [PATCH][next] HID: hid-universal-pidff: Fix spelling mistake "sucessfully" -> "successfully" Colin Ian King
2025-02-12 13:30 ` Tomasz Pakuła [this message]
2025-02-18 21:05 ` Jiri Kosina
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=067382bbfaa4bf9729a8d8ba1a7afb387ba04bd4.camel@gmail.com \
--to=tomasz.pakula.oficjalny@gmail.com \
--cc=bentiss@kernel.org \
--cc=colin.i.king@gmail.com \
--cc=jikos@kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@makarenk.ooo \
/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;
as well as URLs for NNTP newsgroup(s).