tjh.dev / kernel
Linux kernel mirror (for testing) git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel os linux
1
fork

Configure Feed

Select the types of activity you want to include in your feed.

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: Ritvik Gupta <ritvikfoss@gmail.com>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Link: https://lore.kernel.org/r/20250210043937.30952-1-ritvikfoss@gmail.com

authored by

Ritvik Gupta and committed by
Jonathan Corbet 7038f9f2 dc4f75a2

+8 -8
+1 -1
Documentation/filesystems/9p.rst
··· 90 90 91 91 $ diod -f -n -d 0 -S -l 0.0.0.0:9999 -e $PWD 92 92 93 - Optionaly scan your bus if there are more then one usbg gadgets to find their path:: 93 + Optionally scan your bus if there are more then one usbg gadgets to find their path:: 94 94 95 95 $ python $kernel_dir/tools/usb/p9_fwd.py list 96 96
+2 -2
Documentation/filesystems/bcachefs/SubmittingPatches.rst
··· 30 30 === 31 31 32 32 Instead of running your tests locally, when running the full test suite it's 33 - prefereable to let a server farm do it in parallel, and then have the results 33 + preferable to let a server farm do it in parallel, and then have the results 34 34 in a nice test dashboard (which can tell you which failures are new, and 35 35 presents results in a git log view, avoiding the need for most bisecting). 36 36 ··· 68 68 land - use them. Use them judiciously, and not as a replacement for proper 69 69 error handling, but use them. 70 70 71 - - Does it need to be performance tested? Should we add new peformance counters? 71 + - Does it need to be performance tested? Should we add new performance counters? 72 72 73 73 bcachefs has a set of persistent runtime counters which can be viewed with 74 74 the 'bcachefs fs top' command; this should give users a basic idea of what
+1 -1
Documentation/filesystems/coda.rst
··· 141 141 a process P which accessing a Coda file. It makes a system call which 142 142 traps to the OS kernel. Examples of such calls trapping to the kernel 143 143 are ``read``, ``write``, ``open``, ``close``, ``create``, ``mkdir``, 144 - ``rmdir``, ``chmod`` in a Unix ontext. Similar calls exist in the Win32 144 + ``rmdir``, ``chmod`` in a Unix context. Similar calls exist in the Win32 145 145 environment, and are named ``CreateFile``. 146 146 147 147 Generally the operating system handles the request in a virtual
+1 -1
Documentation/filesystems/debugfs.rst
··· 220 220 221 221 A call to debugfs_change_name() will give a new name to an existing debugfs 222 222 file, always in the same directory. The new_name must not exist prior 223 - to the call; the return value is 0 on success and -E... on failuer. 223 + to the call; the return value is 0 on success and -E... on failure. 224 224 Symbolic links can be created with debugfs_create_symlink(). 225 225 226 226 There is one important thing that all debugfs users must take into account:
+1 -1
Documentation/filesystems/netfs_library.rst
··· 515 515 the cache to expand a request in either direction. This allows the cache to 516 516 size the request appropriately for the cache granularity. 517 517 518 - The function is passed poiners to the start and length in its parameters, 518 + The function is passed pointers to the start and length in its parameters, 519 519 plus the size of the file for reference, and adjusts the start and length 520 520 appropriately. It should return one of: 521 521
+1 -1
Documentation/filesystems/xfs/xfs-delayed-logging-design.rst
··· 219 219 of a cycle number - the number of times the log has been overwritten - and the 220 220 offset into the log. A LSN carries the cycle in the upper 32 bits and the 221 221 offset in the lower 32 bits. The offset is in units of "basic blocks" (512 222 - bytes). Hence we can do realtively simple LSN based math to keep track of 222 + bytes). Hence we can do relatively simple LSN based math to keep track of 223 223 available space in the log. 224 224 225 225 Log space accounting is done via a pair of constructs called "grant heads". The
+1 -1
Documentation/filesystems/xfs/xfs-maintainer-entry-profile.rst
··· 93 93 sponsoring work on any part of XFS. 94 94 95 95 - **LTS Maintainer**: Someone who backports and tests bug fixes from 96 - uptream to the LTS kernels. 96 + upstream to the LTS kernels. 97 97 There tend to be six separate LTS trees at any given time. 98 98 99 99 The maintainer for a given LTS release should identify themselves with an