From: krzk@kernel.org
To: linux-nfc@lists.01.org
Subject: [linux-nfc] Re: [PATCH net-next v2 2/3] nfc: s3fwrn5: Fix the misspelling in a comment
Date: Tue, 17 Nov 2020 08:42:32 +0100 [thread overview]
Message-ID: <20201117074232.GD3436@kozik-lap> (raw)
In-Reply-To: 20201117011742epcms2p1fb85ba231b3a1673d97af4bc1479744f@epcms2p1
[-- Attachment #1: Type: text/plain, Size: 270 bytes --]
On Tue, Nov 17, 2020@10:17:42AM +0900, Bongsu Jeon wrote:
> stucture should be replaced by structure.
>
> Signed-off-by: Bongsu Jeon <bongsu.jeon@samsung.com>
I already reviewed it.
Reviewed-by: Krzysztof Kozlowski <krzk@kernel.org>
Best regards,
Krzysztof
reply other threads:[~2020-11-17 7:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20201117074232.GD3436@kozik-lap \
--to=krzk@kernel.org \
--cc=linux-nfc@lists.01.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).