All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ricardo Ribalda <ribalda@chromium.org>
To: trivial@kernel.org
Cc: Ricardo Ribalda <ribalda@chromium.org>, linux-nfs@vger.kernel.org
Subject: [PATCH 7/9] nfsd: Fix typo "accesible"
Date: Thu, 18 Mar 2021 21:22:21 +0100	[thread overview]
Message-ID: <20210318202223.164873-7-ribalda@chromium.org> (raw)
In-Reply-To: <20210318202223.164873-1-ribalda@chromium.org>

Trivial fix.

Cc: linux-nfs@vger.kernel.org
Signed-off-by: Ricardo Ribalda <ribalda@chromium.org>
---
 fs/nfsd/Kconfig | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/fs/nfsd/Kconfig b/fs/nfsd/Kconfig
index 821e5913faee..d160cd4c6f71 100644
--- a/fs/nfsd/Kconfig
+++ b/fs/nfsd/Kconfig
@@ -98,7 +98,7 @@ config NFSD_BLOCKLAYOUT
 	help
 	  This option enables support for the exporting pNFS block layouts
 	  in the kernel's NFS server. The pNFS block layout enables NFS
-	  clients to directly perform I/O to block devices accesible to both
+	  clients to directly perform I/O to block devices accessible to both
 	  the server and the clients.  See RFC 5663 for more details.
 
 	  If unsure, say N.
@@ -112,7 +112,7 @@ config NFSD_SCSILAYOUT
 	help
 	  This option enables support for the exporting pNFS SCSI layouts
 	  in the kernel's NFS server. The pNFS SCSI layout enables NFS
-	  clients to directly perform I/O to SCSI devices accesible to both
+	  clients to directly perform I/O to SCSI devices accessible to both
 	  the server and the clients.  See draft-ietf-nfsv4-scsi-layout for
 	  more details.
 
@@ -126,7 +126,7 @@ config NFSD_FLEXFILELAYOUT
 	  This option enables support for the exporting pNFS Flex File
 	  layouts in the kernel's NFS server. The pNFS Flex File  layout
 	  enables NFS clients to directly perform I/O to NFSv3 devices
-	  accesible to both the server and the clients.  See
+	  accessible to both the server and the clients.  See
 	  draft-ietf-nfsv4-flex-files for more details.
 
 	  Warning, this server implements the bare minimum functionality
-- 
2.31.0.rc2.261.g7f71774620-goog


  parent reply	other threads:[~2021-03-18 20:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210318202223.164873-1-ribalda@chromium.org>
2021-03-18 20:22 ` [PATCH 2/9] media: atomisp: Fix typo "accesible" Ricardo Ribalda
2021-03-18 20:22 ` [Intel-gfx] [PATCH 4/9] drm/i915/error: " Ricardo Ribalda
2021-03-18 20:22 ` Ricardo Ribalda [this message]
2021-03-22 14:21   ` [PATCH 7/9] nfsd: " Chuck Lever III
2021-03-18 20:22 ` [PATCH 8/9] bpf: " Ricardo Ribalda
2021-03-18 20:22 ` [PATCH 9/9] pm-graph: " Ricardo Ribalda
2021-03-22 14:28   ` Rafael J. Wysocki

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=20210318202223.164873-7-ribalda@chromium.org \
    --to=ribalda@chromium.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trivial@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 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.