From: "Namjae Jeon" <namjae.jeon@samsung.com>
To: "'Dan Carpenter'" <dan.carpenter@oracle.com>
Cc: "'Sergey Senozhatsky'" <senozhatsky@chromium.org>,
"'Steve French'" <sfrench@samba.org>,
"'Hyunchul Lee'" <hyc.lee@gmail.com>,
<linux-cifs@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<kernel-janitors@vger.kernel.org>
Subject: RE: [PATCH] ksmbd: delete some stray tabs
Date: Thu, 8 Jul 2021 09:33:20 +0900 [thread overview]
Message-ID: <002001d77390$da160500$8e420f00$@samsung.com> (raw)
In-Reply-To: <YOV+zDoSSwH2oMzG@mwanda>
> These lines are intended one tab too far.
>
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Thanks for your patch. I will apply.
prev parent reply other threads:[~2021-07-08 0:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20210707101627epcas1p46ab0f709390b2f626b429d58400eefb6@epcas1p4.samsung.com>
2021-07-07 10:15 ` [PATCH] ksmbd: delete some stray tabs Dan Carpenter
2021-07-08 0:33 ` Namjae Jeon [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='002001d77390$da160500$8e420f00$@samsung.com' \
--to=namjae.jeon@samsung.com \
--cc=dan.carpenter@oracle.com \
--cc=hyc.lee@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=senozhatsky@chromium.org \
--cc=sfrench@samba.org \
/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).