Commit 7038f9f2 authored by Ritvik Gupta's avatar Ritvik Gupta Committed by Jonathan Corbet
Browse files

documentation/filesystems: fix spelling mistakes 



Corrected the following spelling mistakes,
based on the suggestions by codespell:

1. Optionaly   -> Optionally
2. prefereable -> preferable
3. peformance  -> performance
4. ontext      -> context
5. failuer     -> failure
6. poiners     -> pointers
7. realtively  -> relatively
8. uptream     -> upstream

Signed-off-by: default avatarRitvik Gupta <ritvikfoss@gmail.com>
Acked-by: default avatarRandy Dunlap <rdunlap@infradead.org>
Signed-off-by: default avatarJonathan Corbet <corbet@lwn.net>
Link: https://lore.kernel.org/r/20250210043937.30952-1-ritvikfoss@gmail.com
parent dc4f75a2

Documentation/filesystems/9p.rst

+1 −1
Original line number Diff line number Diff line
@@ -90,7 +90,7 @@ Just start the 9pfs capable network server like diod/nfs-ganesha e.g.:: 


        $ diod -f -n -d 0 -S -l 0.0.0.0:9999 -e $PWD



Optionaly scan your bus if there are more then one usbg gadgets to find their path::

Optionally scan your bus if there are more then one usbg gadgets to find their path::



        $ python $kernel_dir/tools/usb/p9_fwd.py list

Documentation/filesystems/bcachefs/SubmittingPatches.rst

+2 −2
Original line number Diff line number Diff line
@@ -30,7 +30,7 @@ CI: 
===



Instead of running your tests locally, when running the full test suite it's

prefereable to let a server farm do it in parallel, and then have the results

preferable to let a server farm do it in parallel, and then have the results

in a nice test dashboard (which can tell you which failures are new, and

presents results in a git log view, avoiding the need for most bisecting).
@@ -68,7 +68,7 @@ Other things to think about: 
  land - use them. Use them judiciously, and not as a replacement for proper

  error handling, but use them.



- Does it need to be performance tested? Should we add new peformance counters?

- Does it need to be performance tested? Should we add new performance counters?



  bcachefs has a set of persistent runtime counters which can be viewed with

  the 'bcachefs fs top' command; this should give users a basic idea of what

Documentation/filesystems/coda.rst

+1 −1
Original line number Diff line number Diff line
@@ -141,7 +141,7 @@ kernel support. 
  a process P which accessing a Coda file. It makes a system call which

  traps to the OS kernel. Examples of such calls trapping to the kernel

  are ``read``, ``write``, ``open``, ``close``, ``create``, ``mkdir``,

  ``rmdir``, ``chmod`` in a Unix ontext.  Similar calls exist in the Win32

  ``rmdir``, ``chmod`` in a Unix context.  Similar calls exist in the Win32

  environment, and are named ``CreateFile``.



  Generally the operating system handles the request in a virtual

Documentation/filesystems/debugfs.rst

+1 −1
Original line number Diff line number Diff line
@@ -220,7 +220,7 @@ There are a couple of other directory-oriented helper functions:: 


A call to debugfs_change_name() will give a new name to an existing debugfs

file, always in the same directory.  The new_name must not exist prior

to the call; the return value is 0 on success and -E... on failuer.

to the call; the return value is 0 on success and -E... on failure.

Symbolic links can be created with debugfs_create_symlink().



There is one important thing that all debugfs users must take into account:

Documentation/filesystems/netfs_library.rst

+1 −1
Original line number Diff line number Diff line
@@ -515,7 +515,7 @@ The methods defined in the table are: 
   the cache to expand a request in either direction.  This allows the cache to

   size the request appropriately for the cache granularity.



   The function is passed poiners to the start and length in its parameters,

   The function is passed pointers to the start and length in its parameters,

   plus the size of the file for reference, and adjusts the start and length

   appropriately.  It should return one of: