From: divlo <contact@divlo.fr>
To: linux-kernel@vger.kernel.org
Cc: divlo <contact@divlo.fr>
Subject: [PATCH] CHECKPATCH: correct spelling error, from "reqired" to "required"
Date: Fri, 18 Jun 2021 20:55:12 +0200 [thread overview]
Message-ID: <20210618185512.73005-1-contact@divlo.fr> (raw)
Signed-off-by: divlo <contact@divlo.fr>
---
arch/s390/include/uapi/asm/pkey.h | 4 ++--
fs/nfsd/xdr4.h | 6 +++---
scripts/spelling.txt | 1 +
3 files changed, 6 insertions(+), 5 deletions(-)
diff --git a/arch/s390/include/uapi/asm/pkey.h b/arch/s390/include/uapi/asm/pkey.h
index 7349e96d28a0..c04bc9e0614f 100644
--- a/arch/s390/include/uapi/asm/pkey.h
+++ b/arch/s390/include/uapi/asm/pkey.h
@@ -365,7 +365,7 @@ struct pkey_kblob2pkey2 {
* is empty (apqn_entries is 0) the apqn_entries field is updated to the number
* of apqn targets found and the ioctl returns with 0. If apqn_entries is > 0
* but the number of apqn targets does not fit into the list, the apqn_targets
- * field is updatedd with the number of reqired entries but there are no apqn
+ * field is updatedd with the number of required entries but there are no apqn
* values stored in the list and the ioctl returns with ENOSPC. If no matching
* APQN is found, the ioctl returns with 0 but the apqn_entries value is 0.
*/
@@ -403,7 +403,7 @@ struct pkey_apqns4key {
* is empty (apqn_entries is 0) the apqn_entries field is updated to the number
* of apqn targets found and the ioctl returns with 0. If apqn_entries is > 0
* but the number of apqn targets does not fit into the list, the apqn_targets
- * field is updatedd with the number of reqired entries but there are no apqn
+ * field is updatedd with the number of required entries but there are no apqn
* values stored in the list and the ioctl returns with ENOSPC. If no matching
* APQN is found, the ioctl returns with 0 but the apqn_entries value is 0.
*/
diff --git a/fs/nfsd/xdr4.h b/fs/nfsd/xdr4.h
index a7c425254fee..6496d6a2528a 100644
--- a/fs/nfsd/xdr4.h
+++ b/fs/nfsd/xdr4.h
@@ -198,7 +198,7 @@ struct nfsd4_lockt {
struct nfsd4_lock_denied lt_denied;
};
-
+
struct nfsd4_locku {
u32 lu_type;
u32 lu_seqid;
@@ -301,7 +301,7 @@ struct nfsd4_read {
u32 rd_length; /* request */
int rd_vlen;
struct nfsd_file *rd_nf;
-
+
struct svc_rqst *rd_rqstp; /* response */
struct svc_fh *rd_fhp; /* response */
};
@@ -821,7 +821,7 @@ extern void nfsd4_bump_seqid(struct nfsd4_compound_state *, __be32 nfserr);
enum nfsd4_op_flags {
ALLOWED_WITHOUT_FH = 1 << 0, /* No current filehandle required */
ALLOWED_ON_ABSENT_FS = 1 << 1, /* ops processed on absent fs */
- ALLOWED_AS_FIRST_OP = 1 << 2, /* ops reqired first in compound */
+ ALLOWED_AS_FIRST_OP = 1 << 2, /* ops required first in compound */
/* For rfc 5661 section 2.6.3.1.1: */
OP_HANDLES_WRONGSEC = 1 << 3,
OP_IS_PUTFH_LIKE = 1 << 4,
diff --git a/scripts/spelling.txt b/scripts/spelling.txt
index 7b6a01291598..6787c8d1db7f 100644
--- a/scripts/spelling.txt
+++ b/scripts/spelling.txt
@@ -1227,6 +1227,7 @@ replys||replies
reponse||response
representaion||representation
reqeust||request
+reqired||required
reqister||register
requestied||requested
requiere||require
--
2.25.1
reply other threads:[~2021-06-18 19:01 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=20210618185512.73005-1-contact@divlo.fr \
--to=contact@divlo.fr \
--cc=linux-kernel@vger.kernel.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).