From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Bhaskar Chowdhury <unixbhaskar@gmail.com>
Cc: hdegoede@redhat.com, rydberg@bitmath.org,
linux-input@vger.kernel.org, platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org, rdunlap@infradead.org
Subject: Re: [PATCH] Input: Fix a typo
Date: Sun, 21 Mar 2021 20:32:11 -0700 [thread overview]
Message-ID: <YFgPu7YZSv8j1Vuz@google.com> (raw)
In-Reply-To: <20210322022030.3857089-1-unixbhaskar@gmail.com>
On Mon, Mar 22, 2021 at 07:50:30AM +0530, Bhaskar Chowdhury wrote:
>
> s/subsytem/subsystem/
>
> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
Applied, thank you.
--
Dmitry
prev parent reply other threads:[~2021-03-22 3:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 2:20 [PATCH] Input: Fix a typo Bhaskar Chowdhury
2021-03-22 3:00 ` Randy Dunlap
2021-03-22 3:32 ` 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=YFgPu7YZSv8j1Vuz@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=hdegoede@redhat.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=rydberg@bitmath.org \
--cc=unixbhaskar@gmail.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).