From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Binbin Zhou <zhoubinbin@uniontech.com>
Cc: peterhuewe@gmx.de, jgg@ziepe.ca, linux-integrity@vger.kernel.org,
christophe.ricard@gmail.com, zhoubb.aaron@gmail.com
Subject: Re: [PATCH] tpm/st33zp24: fix spelling mistake "drescription" -> "description"
Date: Wed, 17 Jun 2020 00:00:42 +0300 [thread overview]
Message-ID: <20200616210042.GH20943@linux.intel.com> (raw)
In-Reply-To: <20200605033415.8586-1-zhoubinbin@uniontech.com>
On Fri, Jun 05, 2020 at 11:34:15AM +0800, Binbin Zhou wrote:
> Trivial fix, the spelling of "drescription" is incorrect in function comment.
> Fix this.
>
> Signed-off-by: Binbin Zhou <zhoubinbin@uniontech.com>
Acked-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
/Jarkko
next prev parent reply other threads:[~2020-06-16 21:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-05 3:34 [PATCH] tpm/st33zp24: fix spelling mistake "drescription" -> "description" Binbin Zhou
2020-06-16 21:00 ` Jarkko Sakkinen [this message]
2020-06-16 21:03 ` Jarkko Sakkinen
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=20200616210042.GH20943@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=christophe.ricard@gmail.com \
--cc=jgg@ziepe.ca \
--cc=linux-integrity@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=zhoubb.aaron@gmail.com \
--cc=zhoubinbin@uniontech.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).