From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Shivam Chaudhary <cvam0000@gmail.com>
Cc: wse@tuxedocomputers.com, tiwai@suse.de, hdegoede@redhat.com,
eshimanovich@chromium.org, szfabian@bluemarch.art,
tjakobi@math.uni-bielefeld.de, linux-input@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Input: i8042: Fix typo dublicate to duplicate
Date: Wed, 13 Nov 2024 21:21:03 -0800 [thread overview]
Message-ID: <ZzWIv89-BBOqQsxi@google.com> (raw)
In-Reply-To: <20241107174918.78335-1-cvam0000@gmail.com>
On Thu, Nov 07, 2024 at 11:19:18PM +0530, Shivam Chaudhary wrote:
> Fix typo in i8042-acpipnpio.h dublicate -> duplicate.
>
> Signed-off-by: Shivam Chaudhary <cvam0000@gmail.com>
Applied, thank you.
--
Dmitry
prev parent reply other threads:[~2024-11-14 5:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-07 17:49 [PATCH] Input: i8042: Fix typo dublicate to duplicate Shivam Chaudhary
2024-11-14 5:21 ` Dmitry Torokhov [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=ZzWIv89-BBOqQsxi@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=cvam0000@gmail.com \
--cc=eshimanovich@chromium.org \
--cc=hdegoede@redhat.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=szfabian@bluemarch.art \
--cc=tiwai@suse.de \
--cc=tjakobi@math.uni-bielefeld.de \
--cc=wse@tuxedocomputers.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 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).