From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Shubhankar Kuranagatti <shubhankarvk@gmail.com>
Cc: colin.king@canonical.com, dan.carpenter@oracle.com,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
sanjanasrinidhi1810@gmail.com
Subject: Re: [PATCH] drivers: input: misc: ims-pcu.c: Fix usage of spaces
Date: Mon, 24 May 2021 21:15:29 -0700 [thread overview]
Message-ID: <YKx54ddWeILZ70O+@google.com> (raw)
In-Reply-To: <20210428091050.ryr7kxlxre7uhye4@kewl-virtual-machine>
On Wed, Apr 28, 2021 at 02:40:50PM +0530, Shubhankar Kuranagatti wrote:
> Unnecessary spaces have been replaced with tab space
> This is done to maintain code uniformity.
>
> Signed-off-by: Shubhankar Kuranagatti <shubhankarvk@gmail.com>
Applied, thank you.
--
Dmitry
prev parent reply other threads:[~2021-05-25 4:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-28 9:10 [PATCH] drivers: input: misc: ims-pcu.c: Fix usage of spaces Shubhankar Kuranagatti
2021-05-25 4:15 ` 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=YKx54ddWeILZ70O+@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=colin.king@canonical.com \
--cc=dan.carpenter@oracle.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sanjanasrinidhi1810@gmail.com \
--cc=shubhankarvk@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).