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:03:11 +0300 [thread overview]
Message-ID: <20200616210311.GI20943@linux.intel.com> (raw)
In-Reply-To: <20200616210042.GH20943@linux.intel.com>
On Wed, Jun 17, 2020 at 12:00:46AM +0300, Jarkko Sakkinen wrote:
> 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>
Please run your patch with scripts/checkpatch.pl before sending:
» scripts/checkpatch.pl
0001-tpm-st33zp24-fix-spelling-mistake-drescription-descr.patch
WARNING: Possible unwrapped commit description (prefer a maximum 75
chars per line)
#7:
Trivial fix, the spelling of "drescription" is incorrect in function
comment.
total: 0 errors, 1 warnings, 32 lines checked
NOTE: For some of the reported defects, checkpatch may be able to
mechanically convert to the typical style using --fix or
--fix-inplace.
0001-tpm-st33zp24-fix-spelling-mistake-drescription-descr.patch
has style problems, please review.
NOTE: If any of the errors are false positives, please report
them to the maintainer, see CHECKPATCH in MAINTAINERS.
Fix the checkpatch issue and send v2. Thanks.
/Jarkko
prev parent reply other threads:[~2020-06-16 21:03 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
2020-06-16 21:03 ` Jarkko Sakkinen [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=20200616210311.GI20943@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.