* [PATCH 0/9] Documentation: correct lots of spelling errors (series 2)
@ 2023-01-29 23:10 Randy Dunlap
2023-01-29 23:10 ` [PATCH 1/9] Documentation: admin-guide: correct spelling Randy Dunlap
` (5 more replies)
0 siblings, 6 replies; 16+ messages in thread
From: Randy Dunlap @ 2023-01-29 23:10 UTC (permalink / raw)
To: linux-kernel
Cc: Randy Dunlap, Jonathan Corbet, linux-doc, Tejun Heo, Zefan Li,
Johannes Weiner, cgroups, Alasdair Kergon, Mike Snitzer,
dm-devel, Mauro Carvalho Chehab, linux-media, linux-mm,
Dan Williams, Vishal Verma, Dave Jiang, nvdimm, Vinod Koul,
dmaengine, Song Liu, linux-raid, Greg Kroah-Hartman, linux-usb,
Jean Delvare, Guenter Roeck, linux-hwmon, Jiri Pirko,
David S. Miller, Eric Dumazet, Jakub Kicinski, Paolo Abeni,
netdev, Paul E. McKenney, Frederic Weisbecker, Neeraj Upadhyay,
Josh Triplett, rcu, James E.J. Bottomley, Martin K. Petersen,
linux-scsi, sparclinux
Maintainers of specific kernel subsystems are only Cc-ed on their
respective patches, not the entire series. [if all goes well]
These patches are based on linux-next-20230127.
[PATCH 1/9] Documentation: admin-guide: correct spelling
[PATCH 2/9] Documentation: driver-api: correct spelling
[PATCH 3/9] Documentation: hwmon: correct spelling
[PATCH 4/9] Documentation: networking: correct spelling
[PATCH 5/9] Documentation: RCU: correct spelling
[PATCH 6/9] Documentation: scsi/ChangeLog*: correct spelling
[PATCH 7/9] Documentation: scsi: correct spelling
[PATCH 8/9] Documentation: sparc: correct spelling
[PATCH 9/9] Documentation: userspace-api: correct spelling
Documentation/RCU/Design/Expedited-Grace-Periods/Expedited-Grace-Periods.rst | 6 -
Documentation/RCU/Design/Memory-Ordering/Tree-RCU-Memory-Ordering.rst | 2
Documentation/RCU/RTFP.txt | 10 +-
Documentation/RCU/UP.rst | 4
Documentation/RCU/lockdep.rst | 2
Documentation/RCU/torture.rst | 4
Documentation/admin-guide/bcache.rst | 2
Documentation/admin-guide/cgroup-v1/blkio-controller.rst | 2
Documentation/admin-guide/cgroup-v2.rst | 10 +-
Documentation/admin-guide/cifs/usage.rst | 4
Documentation/admin-guide/device-mapper/cache-policies.rst | 2
Documentation/admin-guide/device-mapper/dm-ebs.rst | 2
Documentation/admin-guide/device-mapper/dm-zoned.rst | 2
Documentation/admin-guide/device-mapper/unstriped.rst | 10 +-
Documentation/admin-guide/dynamic-debug-howto.rst | 2
Documentation/admin-guide/gpio/gpio-sim.rst | 2
Documentation/admin-guide/hw-vuln/mds.rst | 4
Documentation/admin-guide/kernel-parameters.txt | 8 -
Documentation/admin-guide/laptops/thinkpad-acpi.rst | 2
Documentation/admin-guide/md.rst | 2
Documentation/admin-guide/media/bttv.rst | 2
Documentation/admin-guide/media/building.rst | 2
Documentation/admin-guide/media/si476x.rst | 2
Documentation/admin-guide/media/vivid.rst | 2
Documentation/admin-guide/mm/hugetlbpage.rst | 2
Documentation/admin-guide/mm/numa_memory_policy.rst | 4
Documentation/admin-guide/perf/hns3-pmu.rst | 2
Documentation/admin-guide/pm/amd-pstate.rst | 2
Documentation/admin-guide/spkguide.txt | 4
Documentation/admin-guide/sysctl/vm.rst | 4
Documentation/admin-guide/sysrq.rst | 2
Documentation/driver-api/dma-buf.rst | 2
Documentation/driver-api/dmaengine/client.rst | 2
Documentation/driver-api/dmaengine/dmatest.rst | 2
Documentation/driver-api/hsi.rst | 4
Documentation/driver-api/io-mapping.rst | 4
Documentation/driver-api/md/md-cluster.rst | 2
Documentation/driver-api/md/raid5-cache.rst | 2
Documentation/driver-api/media/drivers/vidtv.rst | 2
Documentation/driver-api/media/dtv-demux.rst | 2
Documentation/driver-api/media/v4l2-subdev.rst | 4
Documentation/driver-api/mei/nfc.rst | 2
Documentation/driver-api/nfc/nfc-hci.rst | 2
Documentation/driver-api/nvdimm/nvdimm.rst | 2
Documentation/driver-api/nvdimm/security.rst | 2
Documentation/driver-api/pin-control.rst | 2
Documentation/driver-api/pldmfw/index.rst | 2
Documentation/driver-api/serial/driver.rst | 2
Documentation/driver-api/surface_aggregator/ssh.rst | 2
Documentation/driver-api/thermal/intel_powerclamp.rst | 2
Documentation/driver-api/usb/dwc3.rst | 2
Documentation/driver-api/usb/usb3-debug-port.rst | 2
Documentation/hwmon/aht10.rst | 2
Documentation/hwmon/aspeed-pwm-tacho.rst | 2
Documentation/hwmon/corsair-psu.rst | 2
Documentation/hwmon/gsc-hwmon.rst | 6 -
Documentation/hwmon/hwmon-kernel-api.rst | 4
Documentation/hwmon/ltc2978.rst | 2
Documentation/hwmon/max6697.rst | 2
Documentation/hwmon/menf21bmc.rst | 2
Documentation/hwmon/pmbus-core.rst | 2
Documentation/hwmon/sht4x.rst | 2
Documentation/hwmon/smm665.rst | 2
Documentation/hwmon/stpddc60.rst | 2
Documentation/hwmon/vexpress.rst | 2
Documentation/hwmon/via686a.rst | 2
Documentation/networking/af_xdp.rst | 4
Documentation/networking/arcnet-hardware.rst | 2
Documentation/networking/can.rst | 2
Documentation/networking/can_ucan_protocol.rst | 2
Documentation/networking/cdc_mbim.rst | 2
Documentation/networking/device_drivers/atm/iphase.rst | 2
Documentation/networking/device_drivers/can/ctu/ctucanfd-driver.rst | 4
Documentation/networking/device_drivers/can/ctu/fsm_txt_buffer_user.svg | 4
Documentation/networking/device_drivers/ethernet/3com/vortex.rst | 2
Documentation/networking/device_drivers/ethernet/aquantia/atlantic.rst | 6 -
Documentation/networking/device_drivers/ethernet/freescale/dpaa2/mac-phy-support.rst | 2
Documentation/networking/device_drivers/ethernet/marvell/octeontx2.rst | 2
Documentation/networking/device_drivers/ethernet/pensando/ionic.rst | 2
Documentation/networking/device_drivers/ethernet/ti/am65_nuss_cpsw_switchdev.rst | 2
Documentation/networking/device_drivers/ethernet/ti/cpsw_switchdev.rst | 2
Documentation/networking/device_drivers/wwan/iosm.rst | 2
Documentation/networking/devlink/ice.rst | 4
Documentation/networking/devlink/netdevsim.rst | 2
Documentation/networking/devlink/prestera.rst | 2
Documentation/networking/dsa/configuration.rst | 2
Documentation/networking/ethtool-netlink.rst | 6 -
Documentation/networking/gtp.rst | 2
Documentation/networking/ieee802154.rst | 2
Documentation/networking/ip-sysctl.rst | 6 -
Documentation/networking/ipvlan.rst | 2
Documentation/networking/j1939.rst | 2
Documentation/networking/net_failover.rst | 2
Documentation/networking/netconsole.rst | 2
Documentation/networking/page_pool.rst | 6 -
Documentation/networking/phonet.rst | 2
Documentation/networking/phy.rst | 2
Documentation/networking/regulatory.rst | 4
Documentation/networking/rxrpc.rst | 2
Documentation/networking/snmp_counter.rst | 4
Documentation/networking/sysfs-tagging.rst | 2
Documentation/scsi/ChangeLog.lpfc | 36 ++++----
Documentation/scsi/ChangeLog.megaraid | 8 -
Documentation/scsi/ChangeLog.megaraid_sas | 4
Documentation/scsi/ChangeLog.ncr53c8xx | 16 +--
Documentation/scsi/ChangeLog.sym53c8xx | 14 +--
Documentation/scsi/ChangeLog.sym53c8xx_2 | 10 +-
Documentation/scsi/ncr53c8xx.rst | 4
Documentation/scsi/sym53c8xx_2.rst | 2
Documentation/scsi/tcm_qla2xxx.rst | 2
Documentation/scsi/ufs.rst | 2
Documentation/sparc/adi.rst | 4
Documentation/sparc/oradax/dax-hv-api.txt | 44 +++++-----
Documentation/userspace-api/iommufd.rst | 2
Documentation/userspace-api/media/drivers/st-vgxy61.rst | 2
Documentation/userspace-api/media/rc/lirc-set-wideband-receiver.rst | 2
Documentation/userspace-api/media/rc/rc-protos.rst | 2
Documentation/userspace-api/media/rc/rc-tables.rst | 2
Documentation/userspace-api/media/v4l/dev-sliced-vbi.rst | 2
Documentation/userspace-api/media/v4l/ext-ctrls-codec-stateless.rst | 2
Documentation/userspace-api/media/v4l/ext-ctrls-jpeg.rst | 2
Documentation/userspace-api/media/v4l/hist-v4l2.rst | 4
Documentation/userspace-api/media/v4l/pixfmt-yuv-luma.rst | 2
Documentation/userspace-api/media/v4l/vidioc-cropcap.rst | 2
Documentation/userspace-api/seccomp_filter.rst | 2
Documentation/userspace-api/sysfs-platform_profile.rst | 2
126 files changed, 232 insertions(+), 232 deletions(-)
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org
Cc: Tejun Heo <tj@kernel.org>
Cc: Zefan Li <lizefan.x@bytedance.com>
Cc: Johannes Weiner <hannes@cmpxchg.org>
Cc: cgroups@vger.kernel.org
Cc: Alasdair Kergon <agk@redhat.com>
Cc: Mike Snitzer <snitzer@kernel.org>
Cc: dm-devel@redhat.com
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: linux-media@vger.kernel.org
Cc: linux-mm@kvack.org
Cc: Dan Williams <dan.j.williams@intel.com>
Cc: Vishal Verma <vishal.l.verma@intel.com>
Cc: Dave Jiang <dave.jiang@intel.com>
Cc: nvdimm@lists.linux.dev
Cc: Vinod Koul <vkoul@kernel.org>
Cc: dmaengine@vger.kernel.org
Cc: Song Liu <song@kernel.org>
Cc: linux-raid@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-usb@vger.kernel.org
Cc: Jean Delvare <jdelvare@suse.com>
Cc: Guenter Roeck <linux@roeck-us.net>
Cc: linux-hwmon@vger.kernel.org
Cc: Jiri Pirko <jiri@nvidia.com>
Cc: "David S. Miller" <davem@davemloft.net>
Cc: Eric Dumazet <edumazet@google.com>
Cc: Jakub Kicinski <kuba@kernel.org>
Cc: Paolo Abeni <pabeni@redhat.com>
Cc: netdev@vger.kernel.org
Cc: "Paul E. McKenney" <paulmck@kernel.org>
Cc: Frederic Weisbecker <frederic@kernel.org>
Cc: Neeraj Upadhyay <quic_neeraju@quicinc.com>
Cc: Josh Triplett <josh@joshtriplett.org>
Cc: rcu@vger.kernel.org
Cc: "James E.J. Bottomley" <jejb@linux.ibm.com>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: linux-scsi@vger.kernel.org
Cc: sparclinux@vger.kernel.org
^ permalink raw reply [flat|nested] 16+ messages in thread
* [PATCH 1/9] Documentation: admin-guide: correct spelling
2023-01-29 23:10 [PATCH 0/9] Documentation: correct lots of spelling errors (series 2) Randy Dunlap
@ 2023-01-29 23:10 ` Randy Dunlap
2023-01-30 9:35 ` Mukesh Ojha
2023-01-29 23:10 ` [PATCH 2/9] Documentation: driver-api: " Randy Dunlap
` (4 subsequent siblings)
5 siblings, 1 reply; 16+ messages in thread
From: Randy Dunlap @ 2023-01-29 23:10 UTC (permalink / raw)
To: linux-kernel
Cc: Randy Dunlap, Jonathan Corbet, linux-doc, Tejun Heo, Zefan Li,
Johannes Weiner, cgroups, Alasdair Kergon, Mike Snitzer,
dm-devel, Mauro Carvalho Chehab, linux-media, linux-mm
Correct spelling problems for Documentation/admin-guide/ as reported
by codespell.
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org
Cc: Tejun Heo <tj@kernel.org>
Cc: Zefan Li <lizefan.x@bytedance.com>
Cc: Johannes Weiner <hannes@cmpxchg.org>
Cc: cgroups@vger.kernel.org
Cc: Alasdair Kergon <agk@redhat.com>
Cc: Mike Snitzer <snitzer@kernel.org>
Cc: dm-devel@redhat.com
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: linux-media@vger.kernel.org
Cc: linux-mm@kvack.org
---
Documentation/admin-guide/bcache.rst | 2 +-
Documentation/admin-guide/cgroup-v1/blkio-controller.rst | 2 +-
Documentation/admin-guide/cgroup-v2.rst | 10 +++++-----
Documentation/admin-guide/cifs/usage.rst | 4 ++--
Documentation/admin-guide/device-mapper/cache-policies.rst | 2 +-
Documentation/admin-guide/device-mapper/dm-ebs.rst | 2 +-
Documentation/admin-guide/device-mapper/dm-zoned.rst | 2 +-
Documentation/admin-guide/device-mapper/unstriped.rst | 10 +++++-----
Documentation/admin-guide/dynamic-debug-howto.rst | 2 +-
Documentation/admin-guide/gpio/gpio-sim.rst | 2 +-
Documentation/admin-guide/hw-vuln/mds.rst | 4 ++--
Documentation/admin-guide/kernel-parameters.txt | 8 ++++----
Documentation/admin-guide/laptops/thinkpad-acpi.rst | 2 +-
Documentation/admin-guide/md.rst | 2 +-
Documentation/admin-guide/media/bttv.rst | 2 +-
Documentation/admin-guide/media/building.rst | 2 +-
Documentation/admin-guide/media/si476x.rst | 2 +-
Documentation/admin-guide/media/vivid.rst | 2 +-
Documentation/admin-guide/mm/hugetlbpage.rst | 2 +-
Documentation/admin-guide/mm/numa_memory_policy.rst | 4 ++--
Documentation/admin-guide/perf/hns3-pmu.rst | 2 +-
Documentation/admin-guide/pm/amd-pstate.rst | 2 +-
Documentation/admin-guide/spkguide.txt | 4 ++--
Documentation/admin-guide/sysctl/vm.rst | 4 ++--
Documentation/admin-guide/sysrq.rst | 2 +-
25 files changed, 41 insertions(+), 41 deletions(-)
diff -- a/Documentation/admin-guide/cgroup-v2.rst b/Documentation/admin-guide/cgroup-v2.rst
--- a/Documentation/admin-guide/cgroup-v2.rst
+++ b/Documentation/admin-guide/cgroup-v2.rst
@@ -624,7 +624,7 @@ and is an example of this type.
Limits
------
-A child can only consume upto the configured amount of the resource.
+A child can only consume up to the configured amount of the resource.
Limits can be over-committed - the sum of the limits of children can
exceed the amount of resource available to the parent.
@@ -642,11 +642,11 @@ on an IO device and is an example of thi
Protections
-----------
-A cgroup is protected upto the configured amount of the resource
+A cgroup is protected up to the configured amount of the resource
as long as the usages of all its ancestors are under their
protected levels. Protections can be hard guarantees or best effort
soft boundaries. Protections can also be over-committed in which case
-only upto the amount available to the parent is protected among
+only up to the amount available to the parent is protected among
children.
Protections are in the range [0, max] and defaults to 0, which is
@@ -1079,7 +1079,7 @@ All time durations are in microseconds.
$MAX $PERIOD
- which indicates that the group may consume upto $MAX in each
+ which indicates that the group may consume up to $MAX in each
$PERIOD duration. "max" for $MAX indicates no limit. If only
one number is written, $MAX is updated.
@@ -2289,7 +2289,7 @@ Cpuset Interface Files
For a valid partition root with the sibling cpu exclusivity
rule enabled, changes made to "cpuset.cpus" that violate the
exclusivity rule will invalidate the partition as well as its
- sibiling partitions with conflicting cpuset.cpus values. So
+ sibling partitions with conflicting cpuset.cpus values. So
care must be taking in changing "cpuset.cpus".
A valid non-root parent partition may distribute out all its CPUs
diff -- a/Documentation/admin-guide/laptops/thinkpad-acpi.rst b/Documentation/admin-guide/laptops/thinkpad-acpi.rst
--- a/Documentation/admin-guide/laptops/thinkpad-acpi.rst
+++ b/Documentation/admin-guide/laptops/thinkpad-acpi.rst
@@ -1488,7 +1488,7 @@ Example of command to set keyboard langu
Text corresponding to keyboard layout to be set in sysfs are: be(Belgian),
cz(Czech), da(Danish), de(German), en(English), es(Spain), et(Estonian),
fr(French), fr-ch(French(Switzerland)), hu(Hungarian), it(Italy), jp (Japan),
-nl(Dutch), nn(Norway), pl(Polish), pt(portugese), sl(Slovenian), sv(Sweden),
+nl(Dutch), nn(Norway), pl(Polish), pt(portuguese), sl(Slovenian), sv(Sweden),
tr(Turkey)
WWAN Antenna type
diff -- a/Documentation/admin-guide/md.rst b/Documentation/admin-guide/md.rst
--- a/Documentation/admin-guide/md.rst
+++ b/Documentation/admin-guide/md.rst
@@ -317,7 +317,7 @@ All md devices contain:
suspended (not supported yet)
All IO requests will block. The array can be reconfigured.
- Writing this, if accepted, will block until array is quiessent
+ Writing this, if accepted, will block until array is quiescent
readonly
no resync can happen. no superblocks get written.
diff -- a/Documentation/admin-guide/cgroup-v1/blkio-controller.rst b/Documentation/admin-guide/cgroup-v1/blkio-controller.rst
--- a/Documentation/admin-guide/cgroup-v1/blkio-controller.rst
+++ b/Documentation/admin-guide/cgroup-v1/blkio-controller.rst
@@ -106,7 +106,7 @@ Proportional weight policy files
see Documentation/block/bfq-iosched.rst.
blkio.bfq.weight_device
- Specifes per cgroup per device weights, overriding the default group
+ Specifies per cgroup per device weights, overriding the default group
weight. For more details, see Documentation/block/bfq-iosched.rst.
Following is the format::
diff -- a/Documentation/admin-guide/pm/amd-pstate.rst b/Documentation/admin-guide/pm/amd-pstate.rst
--- a/Documentation/admin-guide/pm/amd-pstate.rst
+++ b/Documentation/admin-guide/pm/amd-pstate.rst
@@ -403,7 +403,7 @@ Unit Tests for amd-pstate
* We can introduce more functional or performance tests to align the result together, it will benefit power and performance scale optimization.
-1. Test case decriptions
+1. Test case descriptions
1). Basic tests
diff -- a/Documentation/admin-guide/spkguide.txt b/Documentation/admin-guide/spkguide.txt
--- a/Documentation/admin-guide/spkguide.txt
+++ b/Documentation/admin-guide/spkguide.txt
@@ -1105,8 +1105,8 @@ speakup load
Alternatively, you can add the above line to your file
~/.bashrc or ~/.bash_profile.
-If your system administrator ran himself the script, all the users will be able
-to change from English to the language choosed by root and do directly
+If your system administrator himself ran the script, all the users will be able
+to change from English to the language chosen by root and do directly
speakupconf load (or add this to the ~/.bashrc or
~/.bash_profile file). If there are several languages to handle, the
administrator (or every user) will have to run the first steps until speakupconf
diff -- a/Documentation/admin-guide/device-mapper/cache-policies.rst b/Documentation/admin-guide/device-mapper/cache-policies.rst
--- a/Documentation/admin-guide/device-mapper/cache-policies.rst
+++ b/Documentation/admin-guide/device-mapper/cache-policies.rst
@@ -70,7 +70,7 @@ the entries (each hotspot block covers a
cache block).
All this means smq uses ~25bytes per cache block. Still a lot of
-memory, but a substantial improvement nontheless.
+memory, but a substantial improvement nonetheless.
Level balancing
^^^^^^^^^^^^^^^
diff -- a/Documentation/admin-guide/device-mapper/dm-ebs.rst b/Documentation/admin-guide/device-mapper/dm-ebs.rst
--- a/Documentation/admin-guide/device-mapper/dm-ebs.rst
+++ b/Documentation/admin-guide/device-mapper/dm-ebs.rst
@@ -31,7 +31,7 @@ Mandatory parameters:
Optional parameter:
- <underyling sectors>:
+ <underlying sectors>:
Number of sectors defining the logical block size of <dev path>.
2^N supported, e.g. 8 = emulate 8 sectors of 512 bytes = 4KiB.
If not provided, the logical block size of <dev path> will be used.
diff -- a/Documentation/admin-guide/device-mapper/dm-zoned.rst b/Documentation/admin-guide/device-mapper/dm-zoned.rst
--- a/Documentation/admin-guide/device-mapper/dm-zoned.rst
+++ b/Documentation/admin-guide/device-mapper/dm-zoned.rst
@@ -46,7 +46,7 @@ just like conventional zones.
The zones of the device(s) are separated into 2 types:
1) Metadata zones: these are conventional zones used to store metadata.
-Metadata zones are not reported as useable capacity to the user.
+Metadata zones are not reported as usable capacity to the user.
2) Data zones: all remaining zones, the vast majority of which will be
sequential zones used exclusively to store user data. The conventional
diff -- a/Documentation/admin-guide/device-mapper/unstriped.rst b/Documentation/admin-guide/device-mapper/unstriped.rst
--- a/Documentation/admin-guide/device-mapper/unstriped.rst
+++ b/Documentation/admin-guide/device-mapper/unstriped.rst
@@ -35,7 +35,7 @@ An example of undoing an existing dm-str
This small bash script will setup 4 loop devices and use the existing
striped target to combine the 4 devices into one. It then will use
-the unstriped target ontop of the striped device to access the
+the unstriped target on top of the striped device to access the
individual backing loop devices. We write data to the newly exposed
unstriped devices and verify the data written matches the correct
underlying device on the striped array::
@@ -110,8 +110,8 @@ to get a 92% reduction in read latency u
Example dmsetup usage
=====================
-unstriped ontop of Intel NVMe device that has 2 cores
------------------------------------------------------
+unstriped on top of Intel NVMe device that has 2 cores
+------------------------------------------------------
::
@@ -124,8 +124,8 @@ respectively::
/dev/mapper/nvmset0
/dev/mapper/nvmset1
-unstriped ontop of striped with 4 drives using 128K chunk size
---------------------------------------------------------------
+unstriped on top of striped with 4 drives using 128K chunk size
+---------------------------------------------------------------
::
diff -- a/Documentation/admin-guide/hw-vuln/mds.rst b/Documentation/admin-guide/hw-vuln/mds.rst
--- a/Documentation/admin-guide/hw-vuln/mds.rst
+++ b/Documentation/admin-guide/hw-vuln/mds.rst
@@ -64,8 +64,8 @@ architecture section: :ref:`Documentatio
Attack scenarios
----------------
-Attacks against the MDS vulnerabilities can be mounted from malicious non
-priviledged user space applications running on hosts or guest. Malicious
+Attacks against the MDS vulnerabilities can be mounted from malicious non-
+privileged user space applications running on hosts or guest. Malicious
guest OSes can obviously mount attacks as well.
Contrary to other speculation based vulnerabilities the MDS vulnerability
diff -- a/Documentation/admin-guide/sysctl/vm.rst b/Documentation/admin-guide/sysctl/vm.rst
--- a/Documentation/admin-guide/sysctl/vm.rst
+++ b/Documentation/admin-guide/sysctl/vm.rst
@@ -356,7 +356,7 @@ The lowmem_reserve_ratio is an array. Yo
But, these values are not used directly. The kernel calculates # of protection
pages for each zones from them. These are shown as array of protection pages
-in /proc/zoneinfo like followings. (This is an example of x86-64 box).
+in /proc/zoneinfo like the following. (This is an example of x86-64 box).
Each zone has an array of protection pages like this::
Node 0, zone DMA
@@ -433,7 +433,7 @@ a 2bit error in a memory module) is dete
that cannot be handled by the kernel. In some cases (like the page
still having a valid copy on disk) the kernel will handle the failure
transparently without affecting any applications. But if there is
-no other uptodate copy of the data it will kill to prevent any data
+no other up-to-date copy of the data it will kill to prevent any data
corruptions from propagating.
1: Kill all processes that have the corrupted and not reloadable page mapped
diff -- a/Documentation/admin-guide/bcache.rst b/Documentation/admin-guide/bcache.rst
--- a/Documentation/admin-guide/bcache.rst
+++ b/Documentation/admin-guide/bcache.rst
@@ -204,7 +204,7 @@ For example::
This should present your unmodified backing device data in /dev/loop0
If your cache is in writethrough mode, then you can safely discard the
-cache device without loosing data.
+cache device without losing data.
E) Wiping a cache device
diff -- a/Documentation/admin-guide/sysrq.rst b/Documentation/admin-guide/sysrq.rst
--- a/Documentation/admin-guide/sysrq.rst
+++ b/Documentation/admin-guide/sysrq.rst
@@ -138,7 +138,7 @@ Command Function
``v`` Forcefully restores framebuffer console
``v`` Causes ETM buffer dump [ARM-specific]
-``w`` Dumps tasks that are in uninterruptable (blocked) state.
+``w`` Dumps tasks that are in uninterruptible (blocked) state.
``x`` Used by xmon interface on ppc/powerpc platforms.
Show global PMU Registers on sparc64.
diff -- a/Documentation/admin-guide/cifs/usage.rst b/Documentation/admin-guide/cifs/usage.rst
--- a/Documentation/admin-guide/cifs/usage.rst
+++ b/Documentation/admin-guide/cifs/usage.rst
@@ -399,7 +399,7 @@ A partial list of the supported mount op
sep
if first mount option (after the -o), overrides
the comma as the separator between the mount
- parms. e.g.::
+ parameters. e.g.::
-o user=myname,password=mypassword,domain=mydom
@@ -765,7 +765,7 @@ cifsFYI If set to non-zero value, addi
Some debugging statements are not compiled into the
cifs kernel unless CONFIG_CIFS_DEBUG2 is enabled in the
kernel configuration. cifsFYI may be set to one or
- nore of the following flags (7 sets them all)::
+ more of the following flags (7 sets them all)::
+-----------------------------------------------+------+
| log cifs informational messages | 0x01 |
diff -- a/Documentation/admin-guide/dynamic-debug-howto.rst b/Documentation/admin-guide/dynamic-debug-howto.rst
--- a/Documentation/admin-guide/dynamic-debug-howto.rst
+++ b/Documentation/admin-guide/dynamic-debug-howto.rst
@@ -330,7 +330,7 @@ Examples
// boot-args example, with newlines and comments for readability
Kernel command line: ...
- // see whats going on in dyndbg=value processing
+ // see what's going on in dyndbg=value processing
dynamic_debug.verbose=3
// enable pr_debugs in the btrfs module (can be builtin or loadable)
btrfs.dyndbg="+p"
diff -- a/Documentation/admin-guide/mm/hugetlbpage.rst b/Documentation/admin-guide/mm/hugetlbpage.rst
--- a/Documentation/admin-guide/mm/hugetlbpage.rst
+++ b/Documentation/admin-guide/mm/hugetlbpage.rst
@@ -86,7 +86,7 @@ by increasing or decreasing the value of
Note: When the feature of freeing unused vmemmap pages associated with each
hugetlb page is enabled, we can fail to free the huge pages triggered by
-the user when ths system is under memory pressure. Please try again later.
+the user when the system is under memory pressure. Please try again later.
Pages that are used as huge pages are reserved inside the kernel and cannot
be used for other purposes. Huge pages cannot be swapped out under
diff -- a/Documentation/admin-guide/mm/numa_memory_policy.rst b/Documentation/admin-guide/mm/numa_memory_policy.rst
--- a/Documentation/admin-guide/mm/numa_memory_policy.rst
+++ b/Documentation/admin-guide/mm/numa_memory_policy.rst
@@ -246,7 +246,7 @@ MPOL_INTERLEAVED
interleaved system default policy works in this mode.
MPOL_PREFERRED_MANY
- This mode specifices that the allocation should be preferrably
+ This mode specifies that the allocation should be preferably
satisfied from the nodemask specified in the policy. If there is
a memory pressure on all nodes in the nodemask, the allocation
can fall back to all existing numa nodes. This is effectively
@@ -360,7 +360,7 @@ and NUMA nodes. "Usage" here means one
2) examination of the policy to determine the policy mode and associated node
or node lists, if any, for page allocation. This is considered a "hot
path". Note that for MPOL_BIND, the "usage" extends across the entire
- allocation process, which may sleep during page reclaimation, because the
+ allocation process, which may sleep during page reclamation, because the
BIND policy nodemask is used, by reference, to filter ineligible nodes.
We can avoid taking an extra reference during the usages listed above as
diff -- a/Documentation/admin-guide/gpio/gpio-sim.rst b/Documentation/admin-guide/gpio/gpio-sim.rst
--- a/Documentation/admin-guide/gpio/gpio-sim.rst
+++ b/Documentation/admin-guide/gpio/gpio-sim.rst
@@ -123,7 +123,7 @@ Each simulated GPIO chip creates a separ
directory for each exposed line
(e.g. ``/sys/devices/platform/gpio-sim.X/gpiochipY/``). The name of each group
is of the form: ``'sim_gpioX'`` where X is the offset of the line. Inside each
-group there are two attibutes:
+group there are two attributes:
``pull`` - allows to read and set the current simulated pull setting for
every line, when writing the value must be one of: ``'pull-up'``,
diff -- a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
--- a/Documentation/admin-guide/kernel-parameters.txt
+++ b/Documentation/admin-guide/kernel-parameters.txt
@@ -676,7 +676,7 @@
Sets the size of kernel per-numa memory area for
contiguous memory allocations. A value of 0 disables
per-numa CMA altogether. And If this option is not
- specificed, the default value is 0.
+ specified, the default value is 0.
With per-numa CMA enabled, DMA users on node nid will
first try to allocate buffer from the pernuma area
which is located in node nid, if the allocation fails,
@@ -946,7 +946,7 @@
driver code when a CPU writes to (or reads from) a
random memory location. Note that there exists a class
of memory corruptions problems caused by buggy H/W or
- F/W or by drivers badly programing DMA (basically when
+ F/W or by drivers badly programming DMA (basically when
memory is written at bus level and the CPU MMU is
bypassed) which are not detectable by
CONFIG_DEBUG_PAGEALLOC, hence this option will not help
@@ -1732,7 +1732,7 @@
boot-time allocation of gigantic hugepages is skipped.
hugetlb_free_vmemmap=
- [KNL] Reguires CONFIG_HUGETLB_PAGE_OPTIMIZE_VMEMMAP
+ [KNL] Requires CONFIG_HUGETLB_PAGE_OPTIMIZE_VMEMMAP
enabled.
Control if HugeTLB Vmemmap Optimization (HVO) is enabled.
Allows heavy hugetlb users to free up some more
@@ -3693,7 +3693,7 @@
implementation; requires CONFIG_GENERIC_IDLE_POLL_SETUP
to be effective. This is useful on platforms where the
sleep(SH) or wfi(ARM,ARM64) instructions do not work
- correctly or when doing power measurements to evalute
+ correctly or when doing power measurements to evaluate
the impact of the sleep instructions. This is also
useful when using JTAG debugger.
diff -- a/Documentation/admin-guide/perf/hns3-pmu.rst b/Documentation/admin-guide/perf/hns3-pmu.rst
--- a/Documentation/admin-guide/perf/hns3-pmu.rst
+++ b/Documentation/admin-guide/perf/hns3-pmu.rst
@@ -53,7 +53,7 @@ two events have same value of bits 0~15
event pair. And the bit 16 of config indicates getting counter 0 or
counter 1 of hardware event.
-After getting two values of event pair in usersapce, the formula of
+After getting two values of event pair in userspace, the formula of
computation to calculate real performance data is:::
counter 0 / counter 1
diff -- a/Documentation/admin-guide/media/bttv.rst b/Documentation/admin-guide/media/bttv.rst
--- a/Documentation/admin-guide/media/bttv.rst
+++ b/Documentation/admin-guide/media/bttv.rst
@@ -909,7 +909,7 @@ DE hat diverse Treiber fuer diese Modell
- TVPhone98 (Bt878)
- AVerTV und TVCapture98 w/VCR (Bt 878)
- AVerTVStudio und TVPhone98 w/VCR (Bt878)
- - AVerTV GO Serie (Kein SVideo Input)
+ - AVerTV GO Series (Kein SVideo Input)
- AVerTV98 (BT-878 chip)
- AVerTV98 mit Fernbedienung (BT-878 chip)
- AVerTV/FM98 (BT-878 chip)
diff -- a/Documentation/admin-guide/media/building.rst b/Documentation/admin-guide/media/building.rst
--- a/Documentation/admin-guide/media/building.rst
+++ b/Documentation/admin-guide/media/building.rst
@@ -137,7 +137,7 @@ The ``LIRC user interface`` option adds
from remote controllers.
The ``Support for eBPF programs attached to lirc devices`` option allows
-the usage of special programs (called eBPF) that would allow aplications
+the usage of special programs (called eBPF) that would allow applications
to add extra remote controller decoding functionality to the Linux Kernel.
The ``Remote controller decoders`` option allows selecting the
diff -- a/Documentation/admin-guide/media/si476x.rst b/Documentation/admin-guide/media/si476x.rst
--- a/Documentation/admin-guide/media/si476x.rst
+++ b/Documentation/admin-guide/media/si476x.rst
@@ -142,7 +142,7 @@ The drivers exposes following files:
indicator
0x18 lassi Signed Low side adjacent Channel
Strength indicator
- 0x19 hassi ditto fpr High side
+ 0x19 hassi ditto for High side
0x20 mult Multipath indicator
0x21 dev Frequency deviation
0x24 assi Adjacent channel SSI
diff -- a/Documentation/admin-guide/media/vivid.rst b/Documentation/admin-guide/media/vivid.rst
--- a/Documentation/admin-guide/media/vivid.rst
+++ b/Documentation/admin-guide/media/vivid.rst
@@ -580,7 +580,7 @@ Metadata Capture
----------------
The Metadata capture generates UVC format metadata. The PTS and SCR are
-transmitted based on the values set in vivid contols.
+transmitted based on the values set in vivid controls.
The Metadata device will only work for the Webcam input, it will give
back an error for all other inputs.
^ permalink raw reply [flat|nested] 16+ messages in thread
* [PATCH 2/9] Documentation: driver-api: correct spelling
2023-01-29 23:10 [PATCH 0/9] Documentation: correct lots of spelling errors (series 2) Randy Dunlap
2023-01-29 23:10 ` [PATCH 1/9] Documentation: admin-guide: correct spelling Randy Dunlap
@ 2023-01-29 23:10 ` Randy Dunlap
2023-01-30 19:11 ` Dan Williams
` (2 more replies)
2023-01-29 23:10 ` [PATCH 9/9] Documentation: userspace-api: " Randy Dunlap
` (3 subsequent siblings)
5 siblings, 3 replies; 16+ messages in thread
From: Randy Dunlap @ 2023-01-29 23:10 UTC (permalink / raw)
To: linux-kernel
Cc: Randy Dunlap, Jonathan Corbet, linux-doc, Mauro Carvalho Chehab,
linux-media, Dan Williams, Vishal Verma, Dave Jiang, nvdimm,
Vinod Koul, dmaengine, Song Liu, linux-raid, Greg Kroah-Hartman,
linux-usb
Correct spelling problems for Documentation/driver-api/ as reported
by codespell.
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: linux-media@vger.kernel.org
Cc: Dan Williams <dan.j.williams@intel.com>
Cc: Vishal Verma <vishal.l.verma@intel.com>
Cc: Dave Jiang <dave.jiang@intel.com>
Cc: nvdimm@lists.linux.dev
Cc: Vinod Koul <vkoul@kernel.org>
Cc: dmaengine@vger.kernel.org
Cc: Song Liu <song@kernel.org>
Cc: linux-raid@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-usb@vger.kernel.org
---
Documentation/driver-api/dma-buf.rst | 2 +-
Documentation/driver-api/dmaengine/client.rst | 2 +-
Documentation/driver-api/dmaengine/dmatest.rst | 2 +-
Documentation/driver-api/hsi.rst | 4 ++--
Documentation/driver-api/io-mapping.rst | 4 ++--
Documentation/driver-api/md/md-cluster.rst | 2 +-
Documentation/driver-api/md/raid5-cache.rst | 2 +-
Documentation/driver-api/media/drivers/vidtv.rst | 2 +-
Documentation/driver-api/media/dtv-demux.rst | 2 +-
Documentation/driver-api/media/v4l2-subdev.rst | 4 ++--
Documentation/driver-api/mei/nfc.rst | 2 +-
Documentation/driver-api/nfc/nfc-hci.rst | 2 +-
Documentation/driver-api/nvdimm/nvdimm.rst | 2 +-
Documentation/driver-api/nvdimm/security.rst | 2 +-
Documentation/driver-api/pin-control.rst | 2 +-
Documentation/driver-api/pldmfw/index.rst | 2 +-
Documentation/driver-api/serial/driver.rst | 2 +-
Documentation/driver-api/surface_aggregator/ssh.rst | 2 +-
Documentation/driver-api/thermal/intel_powerclamp.rst | 2 +-
Documentation/driver-api/usb/dwc3.rst | 2 +-
Documentation/driver-api/usb/usb3-debug-port.rst | 2 +-
21 files changed, 24 insertions(+), 24 deletions(-)
diff -- a/Documentation/driver-api/dma-buf.rst b/Documentation/driver-api/dma-buf.rst
--- a/Documentation/driver-api/dma-buf.rst
+++ b/Documentation/driver-api/dma-buf.rst
@@ -264,7 +264,7 @@ through memory management dependencies w
randomly hangs workloads until the timeout kicks in. Workloads, which from
userspace's perspective, do not contain a deadlock. In such a mixed fencing
architecture there is no single entity with knowledge of all dependencies.
-Thefore preventing such deadlocks from within the kernel is not possible.
+Therefore preventing such deadlocks from within the kernel is not possible.
The only solution to avoid dependencies loops is by not allowing indefinite
fences in the kernel. This means:
diff -- a/Documentation/driver-api/hsi.rst b/Documentation/driver-api/hsi.rst
--- a/Documentation/driver-api/hsi.rst
+++ b/Documentation/driver-api/hsi.rst
@@ -4,7 +4,7 @@ High Speed Synchronous Serial Interface
Introduction
---------------
-High Speed Syncronous Interface (HSI) is a fullduplex, low latency protocol,
+High Speed Synchronous Interface (HSI) is a full duplex, low latency protocol,
that is optimized for die-level interconnect between an Application Processor
and a Baseband chipset. It has been specified by the MIPI alliance in 2003 and
implemented by multiple vendors since then.
@@ -52,7 +52,7 @@ hsi-char Device
------------------
Each port automatically registers a generic client driver called hsi_char,
-which provides a charecter device for userspace representing the HSI port.
+which provides a character device for userspace representing the HSI port.
It can be used to communicate via HSI from userspace. Userspace may
configure the hsi_char device using the following ioctl commands:
diff -- a/Documentation/driver-api/mei/nfc.rst b/Documentation/driver-api/mei/nfc.rst
--- a/Documentation/driver-api/mei/nfc.rst
+++ b/Documentation/driver-api/mei/nfc.rst
@@ -3,7 +3,7 @@
MEI NFC
-------
-Some Intel 8 and 9 Serieses chipsets supports NFC devices connected behind
+Some Intel 8 and 9 Series chipsets support NFC devices connected behind
the Intel Management Engine controller.
MEI client bus exposes the NFC chips as NFC phy devices and enables
binding with Microread and NXP PN544 NFC device driver from the Linux NFC
diff -- a/Documentation/driver-api/nfc/nfc-hci.rst b/Documentation/driver-api/nfc/nfc-hci.rst
--- a/Documentation/driver-api/nfc/nfc-hci.rst
+++ b/Documentation/driver-api/nfc/nfc-hci.rst
@@ -150,7 +150,7 @@ LLC
Communication between the CPU and the chip often requires some link layer
protocol. Those are isolated as modules managed by the HCI layer. There are
-currently two modules : nop (raw transfert) and shdlc.
+currently two modules : nop (raw transfer) and shdlc.
A new llc must implement the following functions::
struct nfc_llc_ops {
diff -- a/Documentation/driver-api/serial/driver.rst b/Documentation/driver-api/serial/driver.rst
--- a/Documentation/driver-api/serial/driver.rst
+++ b/Documentation/driver-api/serial/driver.rst
@@ -24,7 +24,7 @@ console support.
Console Support
---------------
-The serial core provides a few helper functions. This includes identifing
+The serial core provides a few helper functions. This includes identifying
the correct port structure (via uart_get_console()) and decoding command line
arguments (uart_parse_options()).
diff -- a/Documentation/driver-api/surface_aggregator/ssh.rst b/Documentation/driver-api/surface_aggregator/ssh.rst
--- a/Documentation/driver-api/surface_aggregator/ssh.rst
+++ b/Documentation/driver-api/surface_aggregator/ssh.rst
@@ -77,7 +77,7 @@ after the frame structure and before the
its own CRC (over all payload bytes). If the payload is not present (i.e.
the frame has ``LEN=0``), the CRC of the payload is still present and will
evaluate to ``0xffff``. The |LEN| field does not include any of the CRCs, it
-equals the number of bytes inbetween the CRC of the frame and the CRC of the
+equals the number of bytes between the CRC of the frame and the CRC of the
payload.
Additionally, the following fixed two-byte sequences are used:
diff -- a/Documentation/driver-api/nvdimm/nvdimm.rst b/Documentation/driver-api/nvdimm/nvdimm.rst
--- a/Documentation/driver-api/nvdimm/nvdimm.rst
+++ b/Documentation/driver-api/nvdimm/nvdimm.rst
@@ -82,7 +82,7 @@ LABEL:
Metadata stored on a DIMM device that partitions and identifies
(persistently names) capacity allocated to different PMEM namespaces. It
also indicates whether an address abstraction like a BTT is applied to
- the namepsace. Note that traditional partition tables, GPT/MBR, are
+ the namespace. Note that traditional partition tables, GPT/MBR, are
layered on top of a PMEM namespace, or an address abstraction like BTT
if present, but partition support is deprecated going forward.
diff -- a/Documentation/driver-api/nvdimm/security.rst b/Documentation/driver-api/nvdimm/security.rst
--- a/Documentation/driver-api/nvdimm/security.rst
+++ b/Documentation/driver-api/nvdimm/security.rst
@@ -83,7 +83,7 @@ passed in.
6. Freeze
---------
The freeze operation does not require any keys. The security config can be
-frozen by a user with root privelege.
+frozen by a user with root privilege.
7. Disable
----------
diff -- a/Documentation/driver-api/thermal/intel_powerclamp.rst b/Documentation/driver-api/thermal/intel_powerclamp.rst
--- a/Documentation/driver-api/thermal/intel_powerclamp.rst
+++ b/Documentation/driver-api/thermal/intel_powerclamp.rst
@@ -85,7 +85,7 @@ migrated, unless the CPU is taken offlin
belong to the offlined CPUs will be terminated immediately.
Running as SCHED_FIFO and relatively high priority, also allows such
-scheme to work for both preemptable and non-preemptable kernels.
+scheme to work for both preemptible and non-preemptible kernels.
Alignment of idle time around jiffies ensures scalability for HZ
values. This effect can be better visualized using a Perf timechart.
The following diagram shows the behavior of kernel thread
diff -- a/Documentation/driver-api/usb/dwc3.rst b/Documentation/driver-api/usb/dwc3.rst
--- a/Documentation/driver-api/usb/dwc3.rst
+++ b/Documentation/driver-api/usb/dwc3.rst
@@ -18,7 +18,7 @@ controller which can be configured in on
4. Hub configuration
Linux currently supports several versions of this controller. In all
-likelyhood, the version in your SoC is already supported. At the time
+likelihood, the version in your SoC is already supported. At the time
of this writing, known tested versions range from 2.02a to 3.10a. As a
rule of thumb, anything above 2.02a should work reliably well.
diff -- a/Documentation/driver-api/usb/usb3-debug-port.rst b/Documentation/driver-api/usb/usb3-debug-port.rst
--- a/Documentation/driver-api/usb/usb3-debug-port.rst
+++ b/Documentation/driver-api/usb/usb3-debug-port.rst
@@ -48,7 +48,7 @@ kernel boot parameter::
"earlyprintk=xdbc"
If there are multiple xHCI controllers in your system, you can
-append a host contoller index to this kernel parameter. This
+append a host controller index to this kernel parameter. This
index starts from 0.
Current design doesn't support DbC runtime suspend/resume. As
diff -- a/Documentation/driver-api/dmaengine/client.rst b/Documentation/driver-api/dmaengine/client.rst
--- a/Documentation/driver-api/dmaengine/client.rst
+++ b/Documentation/driver-api/dmaengine/client.rst
@@ -175,7 +175,7 @@ The details of these operations are:
driver can ask for the pointer, maximum size and the currently used size of
the metadata and can directly update or read it.
- Becasue the DMA driver manages the memory area containing the metadata,
+ Because the DMA driver manages the memory area containing the metadata,
clients must make sure that they do not try to access or get the pointer
after their transfer completion callback has run for the descriptor.
If no completion callback has been defined for the transfer, then the
diff -- a/Documentation/driver-api/dmaengine/dmatest.rst b/Documentation/driver-api/dmaengine/dmatest.rst
--- a/Documentation/driver-api/dmaengine/dmatest.rst
+++ b/Documentation/driver-api/dmaengine/dmatest.rst
@@ -89,7 +89,7 @@ The following command returns the state
% cat /sys/module/dmatest/parameters/run
-To wait for test completion userpace can poll 'run' until it is false, or use
+To wait for test completion userspace can poll 'run' until it is false, or use
the wait parameter. Specifying 'wait=1' when loading the module causes module
initialization to pause until a test run has completed, while reading
/sys/module/dmatest/parameters/wait waits for any running test to complete
diff -- a/Documentation/driver-api/io-mapping.rst b/Documentation/driver-api/io-mapping.rst
--- a/Documentation/driver-api/io-mapping.rst
+++ b/Documentation/driver-api/io-mapping.rst
@@ -44,7 +44,7 @@ This _wc variant returns a write-combini
used with mappings created by io_mapping_create_wc()
Temporary mappings are only valid in the context of the caller. The mapping
-is not guaranteed to be globaly visible.
+is not guaranteed to be globally visible.
io_mapping_map_local_wc() has a side effect on X86 32bit as it disables
migration to make the mapping code work. No caller can rely on this side
@@ -78,7 +78,7 @@ variant, although this may be significan
unsigned long offset)
This works like io_mapping_map_atomic/local_wc() except it has no side
-effects and the pointer is globaly visible.
+effects and the pointer is globally visible.
The mappings are released with::
diff -- a/Documentation/driver-api/media/drivers/vidtv.rst b/Documentation/driver-api/media/drivers/vidtv.rst
--- a/Documentation/driver-api/media/drivers/vidtv.rst
+++ b/Documentation/driver-api/media/drivers/vidtv.rst
@@ -28,7 +28,7 @@ Currently, it consists of:
takes parameters at initialization that will dictate how the simulation
behaves.
-- Code reponsible for encoding a valid MPEG Transport Stream, which is then
+- Code responsible for encoding a valid MPEG Transport Stream, which is then
passed to the bridge driver. This fake stream contains some hardcoded content.
For now, we have a single, audio-only channel containing a single MPEG
Elementary Stream, which in turn contains a SMPTE 302m encoded sine-wave.
diff -- a/Documentation/driver-api/media/dtv-demux.rst b/Documentation/driver-api/media/dtv-demux.rst
--- a/Documentation/driver-api/media/dtv-demux.rst
+++ b/Documentation/driver-api/media/dtv-demux.rst
@@ -24,7 +24,7 @@ unless this is fixed in the HW platform.
The demux kABI only controls front-ends regarding to their connections with
demuxes; the kABI used to set the other front-end parameters, such as
-tuning, are devined via the Digital TV Frontend kABI.
+tuning, are defined via the Digital TV Frontend kABI.
The functions that implement the abstract interface demux should be defined
static or module private and registered to the Demux core for external
diff -- a/Documentation/driver-api/pin-control.rst b/Documentation/driver-api/pin-control.rst
--- a/Documentation/driver-api/pin-control.rst
+++ b/Documentation/driver-api/pin-control.rst
@@ -836,7 +836,7 @@ hardware and shall be put into different
Depending on the exact HW register design, some functions exposed by the
GPIO subsystem may call into the pinctrl subsystem in order to
-co-ordinate register settings across HW modules. In particular, this may
+coordinate register settings across HW modules. In particular, this may
be needed for HW with separate GPIO and pin controller HW modules, where
e.g. GPIO direction is determined by a register in the pin controller HW
module rather than the GPIO HW module.
diff -- a/Documentation/driver-api/pldmfw/index.rst b/Documentation/driver-api/pldmfw/index.rst
--- a/Documentation/driver-api/pldmfw/index.rst
+++ b/Documentation/driver-api/pldmfw/index.rst
@@ -20,7 +20,7 @@ Overview of the ``pldmfw`` library
The ``pldmfw`` library is intended to be used by device drivers for
implementing device flash update based on firmware files following the PLDM
-firwmare file format.
+firmware file format.
It is implemented using an ops table that allows device drivers to provide
the underlying device specific functionality.
diff -- a/Documentation/driver-api/md/md-cluster.rst b/Documentation/driver-api/md/md-cluster.rst
--- a/Documentation/driver-api/md/md-cluster.rst
+++ b/Documentation/driver-api/md/md-cluster.rst
@@ -65,7 +65,7 @@ There are three groups of locks for mana
2.3 new-device management
-------------------------
- A single lock: "no-new-dev" is used to co-ordinate the addition of
+ A single lock: "no-new-dev" is used to coordinate the addition of
new devices - this must be synchronized across the array.
Normally all nodes hold a concurrent-read lock on this device.
diff -- a/Documentation/driver-api/md/raid5-cache.rst b/Documentation/driver-api/md/raid5-cache.rst
--- a/Documentation/driver-api/md/raid5-cache.rst
+++ b/Documentation/driver-api/md/raid5-cache.rst
@@ -81,7 +81,7 @@ The write-through and write-back cache u
is organized as a simple write log. The log consists of 'meta data' and 'data'
pairs. The meta data describes the data. It also includes checksum and sequence
ID for recovery identification. Data can be IO data and parity data. Data is
-checksumed too. The checksum is stored in the meta data ahead of the data. The
+checksummed too. The checksum is stored in the meta data ahead of the data. The
checksum is an optimization because MD can write meta and data freely without
worry about the order. MD superblock has a field pointed to the valid meta data
of log head.
diff -- a/Documentation/driver-api/media/v4l2-subdev.rst b/Documentation/driver-api/media/v4l2-subdev.rst
--- a/Documentation/driver-api/media/v4l2-subdev.rst
+++ b/Documentation/driver-api/media/v4l2-subdev.rst
@@ -321,7 +321,7 @@ response to video node operations. This
hardware from applications. For complex devices, finer-grained control of the
device than what the video nodes offer may be required. In those cases, bridge
drivers that implement :ref:`the media controller API <media_controller>` may
-opt for making the subdevice operations directly accessible from userpace.
+opt for making the subdevice operations directly accessible from userspace.
Device nodes named ``v4l-subdev``\ *X* can be created in ``/dev`` to access
sub-devices directly. If a sub-device supports direct userspace configuration
@@ -574,7 +574,7 @@ issues with subdevice drivers that let t
as they expect to receive the appropriate state as a parameter. To help the
conversion of subdevice drivers to a managed active state without having to
convert all callers at the same time, an additional wrapper layer has been
-added to v4l2_subdev_call(), which handles the NULL case by geting and locking
+added to v4l2_subdev_call(), which handles the NULL case by getting and locking
the callee's active state with :c:func:`v4l2_subdev_lock_and_get_active_state()`,
and unlocking the state after the call.
^ permalink raw reply [flat|nested] 16+ messages in thread
* [PATCH 9/9] Documentation: userspace-api: correct spelling
2023-01-29 23:10 [PATCH 0/9] Documentation: correct lots of spelling errors (series 2) Randy Dunlap
2023-01-29 23:10 ` [PATCH 1/9] Documentation: admin-guide: correct spelling Randy Dunlap
2023-01-29 23:10 ` [PATCH 2/9] Documentation: driver-api: " Randy Dunlap
@ 2023-01-29 23:10 ` Randy Dunlap
2023-01-31 12:10 ` [PATCH 0/9] Documentation: correct lots of spelling errors (series 2) patchwork-bot+netdevbpf
` (2 subsequent siblings)
5 siblings, 0 replies; 16+ messages in thread
From: Randy Dunlap @ 2023-01-29 23:10 UTC (permalink / raw)
To: linux-kernel
Cc: Randy Dunlap, Jonathan Corbet, linux-doc, Sean Young,
Mauro Carvalho Chehab, linux-media
Correct spelling problems for Documentation/userspace-api/ as reported
by codespell.
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org
Cc: Sean Young <sean@mess.org>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: linux-media@vger.kernel.org
---
Documentation/userspace-api/iommufd.rst | 2 +-
Documentation/userspace-api/media/drivers/st-vgxy61.rst | 2 +-
Documentation/userspace-api/media/rc/lirc-set-wideband-receiver.rst | 2 +-
Documentation/userspace-api/media/rc/rc-protos.rst | 2 +-
Documentation/userspace-api/media/rc/rc-tables.rst | 2 +-
Documentation/userspace-api/media/v4l/dev-sliced-vbi.rst | 2 +-
Documentation/userspace-api/media/v4l/ext-ctrls-codec-stateless.rst | 2 +-
Documentation/userspace-api/media/v4l/ext-ctrls-jpeg.rst | 2 +-
Documentation/userspace-api/media/v4l/hist-v4l2.rst | 4 ++--
Documentation/userspace-api/media/v4l/pixfmt-yuv-luma.rst | 2 +-
Documentation/userspace-api/media/v4l/vidioc-cropcap.rst | 2 +-
Documentation/userspace-api/seccomp_filter.rst | 2 +-
Documentation/userspace-api/sysfs-platform_profile.rst | 2 +-
13 files changed, 14 insertions(+), 14 deletions(-)
diff -- a/Documentation/userspace-api/iommufd.rst b/Documentation/userspace-api/iommufd.rst
--- a/Documentation/userspace-api/iommufd.rst
+++ b/Documentation/userspace-api/iommufd.rst
@@ -165,7 +165,7 @@ Multiple io_pagetable-s, through their i
iopt_pages which avoids multi-pinning and double accounting of page
consumption.
-iommufd_ioas is sharable between subsystems, e.g. VFIO and VDPA, as long as
+iommufd_ioas is shareable between subsystems, e.g. VFIO and VDPA, as long as
devices managed by different subsystems are bound to a same iommufd.
IOMMUFD User API
diff -- a/Documentation/userspace-api/media/v4l/dev-sliced-vbi.rst b/Documentation/userspace-api/media/v4l/dev-sliced-vbi.rst
--- a/Documentation/userspace-api/media/v4l/dev-sliced-vbi.rst
+++ b/Documentation/userspace-api/media/v4l/dev-sliced-vbi.rst
@@ -490,7 +490,7 @@ struct v4l2_mpeg_vbi_fmt_ivtv
- An alternate form of the sliced VBI data payload used when 36
lines of sliced VBI data are present. No line masks are provided
in this form of the payload; all valid line mask bits are
- implcitly set.
+ implicitly set.
* - }
-
diff -- a/Documentation/userspace-api/seccomp_filter.rst b/Documentation/userspace-api/seccomp_filter.rst
--- a/Documentation/userspace-api/seccomp_filter.rst
+++ b/Documentation/userspace-api/seccomp_filter.rst
@@ -274,7 +274,7 @@ value will be the injected file descript
The notifying process can be preempted, resulting in the notification being
aborted. This can be problematic when trying to take actions on behalf of the
notifying process that are long-running and typically retryable (mounting a
-filesytem). Alternatively, at filter installation time, the
+filesystem). Alternatively, at filter installation time, the
``SECCOMP_FILTER_FLAG_WAIT_KILLABLE_RECV`` flag can be set. This flag makes it
such that when a user notification is received by the supervisor, the notifying
process will ignore non-fatal signals until the response is sent. Signals that
diff -- a/Documentation/userspace-api/media/v4l/hist-v4l2.rst b/Documentation/userspace-api/media/v4l/hist-v4l2.rst
--- a/Documentation/userspace-api/media/v4l/hist-v4l2.rst
+++ b/Documentation/userspace-api/media/v4l/hist-v4l2.rst
@@ -47,7 +47,7 @@ Codec API was released.
1998-11-08: Many minor changes. Most symbols have been renamed. Some
material changes to struct v4l2_capability.
-1998-11-12: The read/write directon of some ioctls was misdefined.
+1998-11-12: The read/write direction of some ioctls was misdefined.
1998-11-14: ``V4L2_PIX_FMT_RGB24`` changed to ``V4L2_PIX_FMT_BGR24``,
and ``V4L2_PIX_FMT_RGB32`` changed to ``V4L2_PIX_FMT_BGR32``. Audio
@@ -145,7 +145,7 @@ common Linux driver API conventions.
``VIDIOC_G_INFMT``, ``VIDIOC_S_OUTFMT``, ``VIDIOC_G_OUTFMT``,
``VIDIOC_S_VBIFMT`` and ``VIDIOC_G_VBIFMT``. The image format
struct v4l2_format was renamed to struct v4l2_pix_format, while
- struct v4l2_format is now the envelopping structure
+ struct v4l2_format is now the enveloping structure
for all format negotiations.
5. Similar to the changes above, the ``VIDIOC_G_PARM`` and
diff -- a/Documentation/userspace-api/media/v4l/ext-ctrls-codec-stateless.rst b/Documentation/userspace-api/media/v4l/ext-ctrls-codec-stateless.rst
--- a/Documentation/userspace-api/media/v4l/ext-ctrls-codec-stateless.rst
+++ b/Documentation/userspace-api/media/v4l/ext-ctrls-codec-stateless.rst
@@ -1213,7 +1213,7 @@ FWHT Flags
- Luma AC coefficient table index.
* - __s8
- ``y_dc_delta``
- - Luma DC delta vaue.
+ - Luma DC delta value.
* - __s8
- ``y2_dc_delta``
- Y2 block DC delta value.
diff -- a/Documentation/userspace-api/media/v4l/ext-ctrls-jpeg.rst b/Documentation/userspace-api/media/v4l/ext-ctrls-jpeg.rst
--- a/Documentation/userspace-api/media/v4l/ext-ctrls-jpeg.rst
+++ b/Documentation/userspace-api/media/v4l/ext-ctrls-jpeg.rst
@@ -8,7 +8,7 @@ JPEG Control Reference
The JPEG class includes controls for common features of JPEG encoders
and decoders. Currently it includes features for codecs implementing
-progressive baseline DCT compression process with Huffman entrophy
+progressive baseline DCT compression process with Huffman entropy
coding.
diff -- a/Documentation/userspace-api/media/v4l/vidioc-cropcap.rst b/Documentation/userspace-api/media/v4l/vidioc-cropcap.rst
--- a/Documentation/userspace-api/media/v4l/vidioc-cropcap.rst
+++ b/Documentation/userspace-api/media/v4l/vidioc-cropcap.rst
@@ -71,7 +71,7 @@ overlay devices.
- Default cropping rectangle, it shall cover the "whole picture".
Assuming pixel aspect 1/1 this could be for example a 640 × 480
rectangle for NTSC, a 768 × 576 rectangle for PAL and SECAM
- centered over the active picture area. The same co-ordinate system
+ centered over the active picture area. The same coordinate system
as for ``bounds`` is used.
* - struct :c:type:`v4l2_fract`
- ``pixelaspect``
diff -- a/Documentation/userspace-api/media/rc/lirc-set-wideband-receiver.rst b/Documentation/userspace-api/media/rc/lirc-set-wideband-receiver.rst
--- a/Documentation/userspace-api/media/rc/lirc-set-wideband-receiver.rst
+++ b/Documentation/userspace-api/media/rc/lirc-set-wideband-receiver.rst
@@ -43,7 +43,7 @@ reduced range of reception.
.. note::
- Wide band receiver might be implictly enabled if you enable
+ Wide band receiver might be implicitly enabled if you enable
carrier reports. In that case it will be disabled as soon as you disable
carrier reports. Trying to disable wide band receiver while carrier
reports are active will do nothing.
diff -- a/Documentation/userspace-api/media/rc/rc-protos.rst b/Documentation/userspace-api/media/rc/rc-protos.rst
--- a/Documentation/userspace-api/media/rc/rc-protos.rst
+++ b/Documentation/userspace-api/media/rc/rc-protos.rst
@@ -75,7 +75,7 @@ protocol, or the manchester BPF decoder.
- Command
There is a variant of rc5 called either rc5x or extended rc5
-where there the second stop bit is the 6th commmand bit, but inverted.
+where there the second stop bit is the 6th command bit, but inverted.
This is done so it the scancodes and encoding is compatible with existing
schemes. This bit is stored in bit 6 of the scancode, inverted. This is
done to keep it compatible with plain rc-5 where there are two start bits.
diff -- a/Documentation/userspace-api/media/rc/rc-tables.rst b/Documentation/userspace-api/media/rc/rc-tables.rst
--- a/Documentation/userspace-api/media/rc/rc-tables.rst
+++ b/Documentation/userspace-api/media/rc/rc-tables.rst
@@ -628,7 +628,7 @@ the remote via /dev/input/event devices.
- Put device into zoom/full screen mode
- - ZOOM / FULL SCREEN / ZOOM+ / HIDE PANNEL / SWITCH
+ - ZOOM / FULL SCREEN / ZOOM+ / HIDE PANEL / SWITCH
- .. row 80
diff -- a/Documentation/userspace-api/media/v4l/pixfmt-yuv-luma.rst b/Documentation/userspace-api/media/v4l/pixfmt-yuv-luma.rst
--- a/Documentation/userspace-api/media/v4l/pixfmt-yuv-luma.rst
+++ b/Documentation/userspace-api/media/v4l/pixfmt-yuv-luma.rst
@@ -14,7 +14,7 @@ are often referred to as greyscale forma
- In all the tables that follow, bit 7 is the most significant bit in a byte.
- Formats are described with the minimum number of pixels needed to create a
byte-aligned repeating pattern. `...` indicates repetition of the pattern.
- - Y'\ :sub:`x`\ [9:2] denotes bits 9 to 2 of the Y' value for pixel at colum
+ - Y'\ :sub:`x`\ [9:2] denotes bits 9 to 2 of the Y' value for pixel at column
`x`.
- `0` denotes padding bits set to 0.
diff -- a/Documentation/userspace-api/media/drivers/st-vgxy61.rst b/Documentation/userspace-api/media/drivers/st-vgxy61.rst
--- a/Documentation/userspace-api/media/drivers/st-vgxy61.rst
+++ b/Documentation/userspace-api/media/drivers/st-vgxy61.rst
@@ -18,7 +18,7 @@ The ST VGXY61 driver implements the foll
* - HDR linearize
- The merger outputs a long exposure capture as long as it is not
saturated.
- * - HDR substraction
+ * - HDR subtraction
- This involves subtracting the short exposure frame from the long
exposure frame.
* - No HDR
diff -- a/Documentation/userspace-api/sysfs-platform_profile.rst b/Documentation/userspace-api/sysfs-platform_profile.rst
--- a/Documentation/userspace-api/sysfs-platform_profile.rst
+++ b/Documentation/userspace-api/sysfs-platform_profile.rst
@@ -37,6 +37,6 @@ representation onto this fixed set.
If there is no good match when mapping then a new profile name may be
added. Drivers which wish to introduce new profile names must:
- 1. Explain why the existing profile names canot be used.
+ 1. Explain why the existing profile names cannot be used.
2. Add the new profile name, along with a clear description of the
expected behaviour, to the sysfs-platform_profile ABI documentation.
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [PATCH 1/9] Documentation: admin-guide: correct spelling
2023-01-29 23:10 ` [PATCH 1/9] Documentation: admin-guide: correct spelling Randy Dunlap
@ 2023-01-30 9:35 ` Mukesh Ojha
0 siblings, 0 replies; 16+ messages in thread
From: Mukesh Ojha @ 2023-01-30 9:35 UTC (permalink / raw)
To: Randy Dunlap, linux-kernel
Cc: Jonathan Corbet, linux-doc, Tejun Heo, Zefan Li, Johannes Weiner,
cgroups, Alasdair Kergon, Mike Snitzer, dm-devel,
Mauro Carvalho Chehab, linux-media, linux-mm
On 1/30/2023 4:40 AM, Randy Dunlap wrote:
> Correct spelling problems for Documentation/admin-guide/ as reported
> by codespell.
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Jonathan Corbet <corbet@lwn.net>
> Cc: linux-doc@vger.kernel.org
> Cc: Tejun Heo <tj@kernel.org>
> Cc: Zefan Li <lizefan.x@bytedance.com>
> Cc: Johannes Weiner <hannes@cmpxchg.org>
> Cc: cgroups@vger.kernel.org
> Cc: Alasdair Kergon <agk@redhat.com>
> Cc: Mike Snitzer <snitzer@kernel.org>
> Cc: dm-devel@redhat.com
> Cc: Mauro Carvalho Chehab <mchehab@kernel.org>
> Cc: linux-media@vger.kernel.org
> Cc: linux-mm@kvack.org
> ---
> Documentation/admin-guide/bcache.rst | 2 +-
> Documentation/admin-guide/cgroup-v1/blkio-controller.rst | 2 +-
> Documentation/admin-guide/cgroup-v2.rst | 10 +++++-----
> Documentation/admin-guide/cifs/usage.rst | 4 ++--
> Documentation/admin-guide/device-mapper/cache-policies.rst | 2 +-
> Documentation/admin-guide/device-mapper/dm-ebs.rst | 2 +-
> Documentation/admin-guide/device-mapper/dm-zoned.rst | 2 +-
> Documentation/admin-guide/device-mapper/unstriped.rst | 10 +++++-----
> Documentation/admin-guide/dynamic-debug-howto.rst | 2 +-
> Documentation/admin-guide/gpio/gpio-sim.rst | 2 +-
> Documentation/admin-guide/hw-vuln/mds.rst | 4 ++--
> Documentation/admin-guide/kernel-parameters.txt | 8 ++++----
> Documentation/admin-guide/laptops/thinkpad-acpi.rst | 2 +-
> Documentation/admin-guide/md.rst | 2 +-
> Documentation/admin-guide/media/bttv.rst | 2 +-
> Documentation/admin-guide/media/building.rst | 2 +-
> Documentation/admin-guide/media/si476x.rst | 2 +-
> Documentation/admin-guide/media/vivid.rst | 2 +-
> Documentation/admin-guide/mm/hugetlbpage.rst | 2 +-
> Documentation/admin-guide/mm/numa_memory_policy.rst | 4 ++--
> Documentation/admin-guide/perf/hns3-pmu.rst | 2 +-
> Documentation/admin-guide/pm/amd-pstate.rst | 2 +-
> Documentation/admin-guide/spkguide.txt | 4 ++--
> Documentation/admin-guide/sysctl/vm.rst | 4 ++--
> Documentation/admin-guide/sysrq.rst | 2 +-
> 25 files changed, 41 insertions(+), 41 deletions(-)
>
> diff -- a/Documentation/admin-guide/cgroup-v2.rst b/Documentation/admin-guide/cgroup-v2.rst
> --- a/Documentation/admin-guide/cgroup-v2.rst
> +++ b/Documentation/admin-guide/cgroup-v2.rst
> @@ -624,7 +624,7 @@ and is an example of this type.
> Limits
> ------
>
> -A child can only consume upto the configured amount of the resource.
> +A child can only consume up to the configured amount of the resource.
> Limits can be over-committed - the sum of the limits of children can
> exceed the amount of resource available to the parent.
>
> @@ -642,11 +642,11 @@ on an IO device and is an example of thi
> Protections
> -----------
>
> -A cgroup is protected upto the configured amount of the resource
> +A cgroup is protected up to the configured amount of the resource
> as long as the usages of all its ancestors are under their
> protected levels. Protections can be hard guarantees or best effort
> soft boundaries. Protections can also be over-committed in which case
> -only upto the amount available to the parent is protected among
> +only up to the amount available to the parent is protected among
> children.
>
> Protections are in the range [0, max] and defaults to 0, which is
> @@ -1079,7 +1079,7 @@ All time durations are in microseconds.
>
> $MAX $PERIOD
>
> - which indicates that the group may consume upto $MAX in each
> + which indicates that the group may consume up to $MAX in each
> $PERIOD duration. "max" for $MAX indicates no limit. If only
> one number is written, $MAX is updated.
>
> @@ -2289,7 +2289,7 @@ Cpuset Interface Files
> For a valid partition root with the sibling cpu exclusivity
> rule enabled, changes made to "cpuset.cpus" that violate the
> exclusivity rule will invalidate the partition as well as its
> - sibiling partitions with conflicting cpuset.cpus values. So
> + sibling partitions with conflicting cpuset.cpus values. So
> care must be taking in changing "cpuset.cpus".
>
> A valid non-root parent partition may distribute out all its CPUs
> diff -- a/Documentation/admin-guide/laptops/thinkpad-acpi.rst b/Documentation/admin-guide/laptops/thinkpad-acpi.rst
> --- a/Documentation/admin-guide/laptops/thinkpad-acpi.rst
> +++ b/Documentation/admin-guide/laptops/thinkpad-acpi.rst
> @@ -1488,7 +1488,7 @@ Example of command to set keyboard langu
> Text corresponding to keyboard layout to be set in sysfs are: be(Belgian),
> cz(Czech), da(Danish), de(German), en(English), es(Spain), et(Estonian),
> fr(French), fr-ch(French(Switzerland)), hu(Hungarian), it(Italy), jp (Japan),
> -nl(Dutch), nn(Norway), pl(Polish), pt(portugese), sl(Slovenian), sv(Sweden),
> +nl(Dutch), nn(Norway), pl(Polish), pt(portuguese), sl(Slovenian), sv(Sweden),
> tr(Turkey)
>
> WWAN Antenna type
> diff -- a/Documentation/admin-guide/md.rst b/Documentation/admin-guide/md.rst
> --- a/Documentation/admin-guide/md.rst
> +++ b/Documentation/admin-guide/md.rst
> @@ -317,7 +317,7 @@ All md devices contain:
> suspended (not supported yet)
> All IO requests will block. The array can be reconfigured.
>
> - Writing this, if accepted, will block until array is quiessent
> + Writing this, if accepted, will block until array is quiescent
>
> readonly
> no resync can happen. no superblocks get written.
> diff -- a/Documentation/admin-guide/cgroup-v1/blkio-controller.rst b/Documentation/admin-guide/cgroup-v1/blkio-controller.rst
> --- a/Documentation/admin-guide/cgroup-v1/blkio-controller.rst
> +++ b/Documentation/admin-guide/cgroup-v1/blkio-controller.rst
> @@ -106,7 +106,7 @@ Proportional weight policy files
> see Documentation/block/bfq-iosched.rst.
>
> blkio.bfq.weight_device
> - Specifes per cgroup per device weights, overriding the default group
> + Specifies per cgroup per device weights, overriding the default group
> weight. For more details, see Documentation/block/bfq-iosched.rst.
>
> Following is the format::
> diff -- a/Documentation/admin-guide/pm/amd-pstate.rst b/Documentation/admin-guide/pm/amd-pstate.rst
> --- a/Documentation/admin-guide/pm/amd-pstate.rst
> +++ b/Documentation/admin-guide/pm/amd-pstate.rst
> @@ -403,7 +403,7 @@ Unit Tests for amd-pstate
>
> * We can introduce more functional or performance tests to align the result together, it will benefit power and performance scale optimization.
>
> -1. Test case decriptions
> +1. Test case descriptions
>
> 1). Basic tests
>
> diff -- a/Documentation/admin-guide/spkguide.txt b/Documentation/admin-guide/spkguide.txt
> --- a/Documentation/admin-guide/spkguide.txt
> +++ b/Documentation/admin-guide/spkguide.txt
> @@ -1105,8 +1105,8 @@ speakup load
> Alternatively, you can add the above line to your file
> ~/.bashrc or ~/.bash_profile.
>
> -If your system administrator ran himself the script, all the users will be able
> -to change from English to the language choosed by root and do directly
> +If your system administrator himself ran the script, all the users will be able
> +to change from English to the language chosen by root and do directly
> speakupconf load (or add this to the ~/.bashrc or
> ~/.bash_profile file). If there are several languages to handle, the
> administrator (or every user) will have to run the first steps until speakupconf
> diff -- a/Documentation/admin-guide/device-mapper/cache-policies.rst b/Documentation/admin-guide/device-mapper/cache-policies.rst
> --- a/Documentation/admin-guide/device-mapper/cache-policies.rst
> +++ b/Documentation/admin-guide/device-mapper/cache-policies.rst
> @@ -70,7 +70,7 @@ the entries (each hotspot block covers a
> cache block).
>
> All this means smq uses ~25bytes per cache block. Still a lot of
> -memory, but a substantial improvement nontheless.
> +memory, but a substantial improvement nonetheless.
>
> Level balancing
> ^^^^^^^^^^^^^^^
> diff -- a/Documentation/admin-guide/device-mapper/dm-ebs.rst b/Documentation/admin-guide/device-mapper/dm-ebs.rst
> --- a/Documentation/admin-guide/device-mapper/dm-ebs.rst
> +++ b/Documentation/admin-guide/device-mapper/dm-ebs.rst
> @@ -31,7 +31,7 @@ Mandatory parameters:
>
> Optional parameter:
>
> - <underyling sectors>:
> + <underlying sectors>:
> Number of sectors defining the logical block size of <dev path>.
> 2^N supported, e.g. 8 = emulate 8 sectors of 512 bytes = 4KiB.
> If not provided, the logical block size of <dev path> will be used.
> diff -- a/Documentation/admin-guide/device-mapper/dm-zoned.rst b/Documentation/admin-guide/device-mapper/dm-zoned.rst
> --- a/Documentation/admin-guide/device-mapper/dm-zoned.rst
> +++ b/Documentation/admin-guide/device-mapper/dm-zoned.rst
> @@ -46,7 +46,7 @@ just like conventional zones.
> The zones of the device(s) are separated into 2 types:
>
> 1) Metadata zones: these are conventional zones used to store metadata.
> -Metadata zones are not reported as useable capacity to the user.
> +Metadata zones are not reported as usable capacity to the user.
>
> 2) Data zones: all remaining zones, the vast majority of which will be
> sequential zones used exclusively to store user data. The conventional
> diff -- a/Documentation/admin-guide/device-mapper/unstriped.rst b/Documentation/admin-guide/device-mapper/unstriped.rst
> --- a/Documentation/admin-guide/device-mapper/unstriped.rst
> +++ b/Documentation/admin-guide/device-mapper/unstriped.rst
> @@ -35,7 +35,7 @@ An example of undoing an existing dm-str
>
> This small bash script will setup 4 loop devices and use the existing
> striped target to combine the 4 devices into one. It then will use
> -the unstriped target ontop of the striped device to access the
> +the unstriped target on top of the striped device to access the
> individual backing loop devices. We write data to the newly exposed
> unstriped devices and verify the data written matches the correct
> underlying device on the striped array::
> @@ -110,8 +110,8 @@ to get a 92% reduction in read latency u
> Example dmsetup usage
> =====================
>
> -unstriped ontop of Intel NVMe device that has 2 cores
> ------------------------------------------------------
> +unstriped on top of Intel NVMe device that has 2 cores
> +------------------------------------------------------
>
> ::
>
> @@ -124,8 +124,8 @@ respectively::
> /dev/mapper/nvmset0
> /dev/mapper/nvmset1
>
> -unstriped ontop of striped with 4 drives using 128K chunk size
> ---------------------------------------------------------------
> +unstriped on top of striped with 4 drives using 128K chunk size
> +---------------------------------------------------------------
>
> ::
>
> diff -- a/Documentation/admin-guide/hw-vuln/mds.rst b/Documentation/admin-guide/hw-vuln/mds.rst
> --- a/Documentation/admin-guide/hw-vuln/mds.rst
> +++ b/Documentation/admin-guide/hw-vuln/mds.rst
> @@ -64,8 +64,8 @@ architecture section: :ref:`Documentatio
> Attack scenarios
> ----------------
>
> -Attacks against the MDS vulnerabilities can be mounted from malicious non
> -priviledged user space applications running on hosts or guest. Malicious
> +Attacks against the MDS vulnerabilities can be mounted from malicious non-
> +privileged user space applications running on hosts or guest. Malicious
> guest OSes can obviously mount attacks as well.
>
> Contrary to other speculation based vulnerabilities the MDS vulnerability
> diff -- a/Documentation/admin-guide/sysctl/vm.rst b/Documentation/admin-guide/sysctl/vm.rst
> --- a/Documentation/admin-guide/sysctl/vm.rst
> +++ b/Documentation/admin-guide/sysctl/vm.rst
> @@ -356,7 +356,7 @@ The lowmem_reserve_ratio is an array. Yo
>
> But, these values are not used directly. The kernel calculates # of protection
> pages for each zones from them. These are shown as array of protection pages
> -in /proc/zoneinfo like followings. (This is an example of x86-64 box).
> +in /proc/zoneinfo like the following. (This is an example of x86-64 box).
> Each zone has an array of protection pages like this::
>
> Node 0, zone DMA
> @@ -433,7 +433,7 @@ a 2bit error in a memory module) is dete
> that cannot be handled by the kernel. In some cases (like the page
> still having a valid copy on disk) the kernel will handle the failure
> transparently without affecting any applications. But if there is
> -no other uptodate copy of the data it will kill to prevent any data
> +no other up-to-date copy of the data it will kill to prevent any data
> corruptions from propagating.
>
> 1: Kill all processes that have the corrupted and not reloadable page mapped
> diff -- a/Documentation/admin-guide/bcache.rst b/Documentation/admin-guide/bcache.rst
> --- a/Documentation/admin-guide/bcache.rst
> +++ b/Documentation/admin-guide/bcache.rst
> @@ -204,7 +204,7 @@ For example::
> This should present your unmodified backing device data in /dev/loop0
>
> If your cache is in writethrough mode, then you can safely discard the
> -cache device without loosing data.
> +cache device without losing data.
>
>
> E) Wiping a cache device
> diff -- a/Documentation/admin-guide/sysrq.rst b/Documentation/admin-guide/sysrq.rst
> --- a/Documentation/admin-guide/sysrq.rst
> +++ b/Documentation/admin-guide/sysrq.rst
> @@ -138,7 +138,7 @@ Command Function
> ``v`` Forcefully restores framebuffer console
> ``v`` Causes ETM buffer dump [ARM-specific]
>
> -``w`` Dumps tasks that are in uninterruptable (blocked) state.
> +``w`` Dumps tasks that are in uninterruptible (blocked) state.
>
> ``x`` Used by xmon interface on ppc/powerpc platforms.
> Show global PMU Registers on sparc64.
> diff -- a/Documentation/admin-guide/cifs/usage.rst b/Documentation/admin-guide/cifs/usage.rst
> --- a/Documentation/admin-guide/cifs/usage.rst
> +++ b/Documentation/admin-guide/cifs/usage.rst
> @@ -399,7 +399,7 @@ A partial list of the supported mount op
> sep
> if first mount option (after the -o), overrides
> the comma as the separator between the mount
> - parms. e.g.::
> + parameters. e.g.::
>
> -o user=myname,password=mypassword,domain=mydom
>
> @@ -765,7 +765,7 @@ cifsFYI If set to non-zero value, addi
> Some debugging statements are not compiled into the
> cifs kernel unless CONFIG_CIFS_DEBUG2 is enabled in the
> kernel configuration. cifsFYI may be set to one or
> - nore of the following flags (7 sets them all)::
> + more of the following flags (7 sets them all)::
>
> +-----------------------------------------------+------+
> | log cifs informational messages | 0x01 |
> diff -- a/Documentation/admin-guide/dynamic-debug-howto.rst b/Documentation/admin-guide/dynamic-debug-howto.rst
> --- a/Documentation/admin-guide/dynamic-debug-howto.rst
> +++ b/Documentation/admin-guide/dynamic-debug-howto.rst
> @@ -330,7 +330,7 @@ Examples
>
> // boot-args example, with newlines and comments for readability
> Kernel command line: ...
> - // see whats going on in dyndbg=value processing
> + // see what's going on in dyndbg=value processing
> dynamic_debug.verbose=3
> // enable pr_debugs in the btrfs module (can be builtin or loadable)
> btrfs.dyndbg="+p"
> diff -- a/Documentation/admin-guide/mm/hugetlbpage.rst b/Documentation/admin-guide/mm/hugetlbpage.rst
> --- a/Documentation/admin-guide/mm/hugetlbpage.rst
> +++ b/Documentation/admin-guide/mm/hugetlbpage.rst
> @@ -86,7 +86,7 @@ by increasing or decreasing the value of
>
> Note: When the feature of freeing unused vmemmap pages associated with each
> hugetlb page is enabled, we can fail to free the huge pages triggered by
> -the user when ths system is under memory pressure. Please try again later.
> +the user when the system is under memory pressure. Please try again later.
My eye almost missed 'ths' :-)
>
> Pages that are used as huge pages are reserved inside the kernel and cannot
> be used for other purposes. Huge pages cannot be swapped out under
> diff -- a/Documentation/admin-guide/mm/numa_memory_policy.rst b/Documentation/admin-guide/mm/numa_memory_policy.rst
> --- a/Documentation/admin-guide/mm/numa_memory_policy.rst
> +++ b/Documentation/admin-guide/mm/numa_memory_policy.rst
> @@ -246,7 +246,7 @@ MPOL_INTERLEAVED
> interleaved system default policy works in this mode.
>
> MPOL_PREFERRED_MANY
> - This mode specifices that the allocation should be preferrably
> + This mode specifies that the allocation should be preferably
> satisfied from the nodemask specified in the policy. If there is
> a memory pressure on all nodes in the nodemask, the allocation
> can fall back to all existing numa nodes. This is effectively
> @@ -360,7 +360,7 @@ and NUMA nodes. "Usage" here means one
> 2) examination of the policy to determine the policy mode and associated node
> or node lists, if any, for page allocation. This is considered a "hot
> path". Note that for MPOL_BIND, the "usage" extends across the entire
> - allocation process, which may sleep during page reclaimation, because the
> + allocation process, which may sleep during page reclamation, because the
> BIND policy nodemask is used, by reference, to filter ineligible nodes.
>
> We can avoid taking an extra reference during the usages listed above as
> diff -- a/Documentation/admin-guide/gpio/gpio-sim.rst b/Documentation/admin-guide/gpio/gpio-sim.rst
> --- a/Documentation/admin-guide/gpio/gpio-sim.rst
> +++ b/Documentation/admin-guide/gpio/gpio-sim.rst
> @@ -123,7 +123,7 @@ Each simulated GPIO chip creates a separ
> directory for each exposed line
> (e.g. ``/sys/devices/platform/gpio-sim.X/gpiochipY/``). The name of each group
> is of the form: ``'sim_gpioX'`` where X is the offset of the line. Inside each
> -group there are two attibutes:
> +group there are two attributes:
>
> ``pull`` - allows to read and set the current simulated pull setting for
> every line, when writing the value must be one of: ``'pull-up'``,
> diff -- a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
> --- a/Documentation/admin-guide/kernel-parameters.txt
> +++ b/Documentation/admin-guide/kernel-parameters.txt
> @@ -676,7 +676,7 @@
> Sets the size of kernel per-numa memory area for
> contiguous memory allocations. A value of 0 disables
> per-numa CMA altogether. And If this option is not
> - specificed, the default value is 0.
> + specified, the default value is 0.
> With per-numa CMA enabled, DMA users on node nid will
> first try to allocate buffer from the pernuma area
> which is located in node nid, if the allocation fails,
> @@ -946,7 +946,7 @@
> driver code when a CPU writes to (or reads from) a
> random memory location. Note that there exists a class
> of memory corruptions problems caused by buggy H/W or
> - F/W or by drivers badly programing DMA (basically when
> + F/W or by drivers badly programming DMA (basically when
> memory is written at bus level and the CPU MMU is
> bypassed) which are not detectable by
> CONFIG_DEBUG_PAGEALLOC, hence this option will not help
> @@ -1732,7 +1732,7 @@
> boot-time allocation of gigantic hugepages is skipped.
>
> hugetlb_free_vmemmap=
> - [KNL] Reguires CONFIG_HUGETLB_PAGE_OPTIMIZE_VMEMMAP
> + [KNL] Requires CONFIG_HUGETLB_PAGE_OPTIMIZE_VMEMMAP
> enabled.
> Control if HugeTLB Vmemmap Optimization (HVO) is enabled.
> Allows heavy hugetlb users to free up some more
> @@ -3693,7 +3693,7 @@
> implementation; requires CONFIG_GENERIC_IDLE_POLL_SETUP
> to be effective. This is useful on platforms where the
> sleep(SH) or wfi(ARM,ARM64) instructions do not work
> - correctly or when doing power measurements to evalute
> + correctly or when doing power measurements to evaluate
> the impact of the sleep instructions. This is also
> useful when using JTAG debugger.
>
> diff -- a/Documentation/admin-guide/perf/hns3-pmu.rst b/Documentation/admin-guide/perf/hns3-pmu.rst
> --- a/Documentation/admin-guide/perf/hns3-pmu.rst
> +++ b/Documentation/admin-guide/perf/hns3-pmu.rst
> @@ -53,7 +53,7 @@ two events have same value of bits 0~15
> event pair. And the bit 16 of config indicates getting counter 0 or
> counter 1 of hardware event.
>
> -After getting two values of event pair in usersapce, the formula of
> +After getting two values of event pair in userspace, the formula of
> computation to calculate real performance data is:::
>
> counter 0 / counter 1
> diff -- a/Documentation/admin-guide/media/bttv.rst b/Documentation/admin-guide/media/bttv.rst
> --- a/Documentation/admin-guide/media/bttv.rst
> +++ b/Documentation/admin-guide/media/bttv.rst
> @@ -909,7 +909,7 @@ DE hat diverse Treiber fuer diese Modell
> - TVPhone98 (Bt878)
> - AVerTV und TVCapture98 w/VCR (Bt 878)
> - AVerTVStudio und TVPhone98 w/VCR (Bt878)
> - - AVerTV GO Serie (Kein SVideo Input)
> + - AVerTV GO Series (Kein SVideo Input)
> - AVerTV98 (BT-878 chip)
> - AVerTV98 mit Fernbedienung (BT-878 chip)
> - AVerTV/FM98 (BT-878 chip)
> diff -- a/Documentation/admin-guide/media/building.rst b/Documentation/admin-guide/media/building.rst
> --- a/Documentation/admin-guide/media/building.rst
> +++ b/Documentation/admin-guide/media/building.rst
> @@ -137,7 +137,7 @@ The ``LIRC user interface`` option adds
> from remote controllers.
>
> The ``Support for eBPF programs attached to lirc devices`` option allows
> -the usage of special programs (called eBPF) that would allow aplications
> +the usage of special programs (called eBPF) that would allow applications
> to add extra remote controller decoding functionality to the Linux Kernel.
>
> The ``Remote controller decoders`` option allows selecting the
> diff -- a/Documentation/admin-guide/media/si476x.rst b/Documentation/admin-guide/media/si476x.rst
> --- a/Documentation/admin-guide/media/si476x.rst
> +++ b/Documentation/admin-guide/media/si476x.rst
> @@ -142,7 +142,7 @@ The drivers exposes following files:
> indicator
> 0x18 lassi Signed Low side adjacent Channel
> Strength indicator
> - 0x19 hassi ditto fpr High side
> + 0x19 hassi ditto for High side
> 0x20 mult Multipath indicator
> 0x21 dev Frequency deviation
> 0x24 assi Adjacent channel SSI
> diff -- a/Documentation/admin-guide/media/vivid.rst b/Documentation/admin-guide/media/vivid.rst
> --- a/Documentation/admin-guide/media/vivid.rst
> +++ b/Documentation/admin-guide/media/vivid.rst
> @@ -580,7 +580,7 @@ Metadata Capture
> ----------------
>
> The Metadata capture generates UVC format metadata. The PTS and SCR are
> -transmitted based on the values set in vivid contols.
> +transmitted based on the values set in vivid controls.
>
> The Metadata device will only work for the Webcam input, it will give
> back an error for all other inputs.
Reviewed-by: Mukesh Ojha <quic_mojha@quicinc.com>
-Mukesh
^ permalink raw reply [flat|nested] 16+ messages in thread
* RE: [PATCH 2/9] Documentation: driver-api: correct spelling
2023-01-29 23:10 ` [PATCH 2/9] Documentation: driver-api: " Randy Dunlap
@ 2023-01-30 19:11 ` Dan Williams
2023-01-30 19:45 ` Song Liu
2023-01-31 9:10 ` Greg Kroah-Hartman
2 siblings, 0 replies; 16+ messages in thread
From: Dan Williams @ 2023-01-30 19:11 UTC (permalink / raw)
To: Randy Dunlap, linux-kernel
Cc: Randy Dunlap, Jonathan Corbet, linux-doc, Mauro Carvalho Chehab,
linux-media, Dan Williams, Vishal Verma, Dave Jiang, nvdimm,
Vinod Koul, dmaengine, Song Liu, linux-raid, Greg Kroah-Hartman,
linux-usb
Randy Dunlap wrote:
> Correct spelling problems for Documentation/driver-api/ as reported
> by codespell.
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Jonathan Corbet <corbet@lwn.net>
> Cc: linux-doc@vger.kernel.org
> Cc: Mauro Carvalho Chehab <mchehab@kernel.org>
> Cc: linux-media@vger.kernel.org
> Cc: Dan Williams <dan.j.williams@intel.com>
> Cc: Vishal Verma <vishal.l.verma@intel.com>
> Cc: Dave Jiang <dave.jiang@intel.com>
> Cc: nvdimm@lists.linux.dev
> Cc: Vinod Koul <vkoul@kernel.org>
> Cc: dmaengine@vger.kernel.org
> Cc: Song Liu <song@kernel.org>
> Cc: linux-raid@vger.kernel.org
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Cc: linux-usb@vger.kernel.org
> ---
> Documentation/driver-api/nvdimm/nvdimm.rst | 2 +-
> Documentation/driver-api/nvdimm/security.rst | 2 +-
For the nvdimm bits,
Acked-by: Dan Williams <dan.j.williams@intel.com>
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [PATCH 2/9] Documentation: driver-api: correct spelling
2023-01-29 23:10 ` [PATCH 2/9] Documentation: driver-api: " Randy Dunlap
2023-01-30 19:11 ` Dan Williams
@ 2023-01-30 19:45 ` Song Liu
2023-01-31 9:10 ` Greg Kroah-Hartman
2 siblings, 0 replies; 16+ messages in thread
From: Song Liu @ 2023-01-30 19:45 UTC (permalink / raw)
To: Randy Dunlap
Cc: linux-kernel, Jonathan Corbet, linux-doc, Mauro Carvalho Chehab,
linux-media, Dan Williams, Vishal Verma, Dave Jiang, nvdimm,
Vinod Koul, dmaengine, linux-raid, Greg Kroah-Hartman, linux-usb
On Sun, Jan 29, 2023 at 3:11 PM Randy Dunlap <rdunlap@infradead.org> wrote:
>
> Correct spelling problems for Documentation/driver-api/ as reported
> by codespell.
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Jonathan Corbet <corbet@lwn.net>
> Cc: linux-doc@vger.kernel.org
> Cc: Mauro Carvalho Chehab <mchehab@kernel.org>
> Cc: linux-media@vger.kernel.org
> Cc: Dan Williams <dan.j.williams@intel.com>
> Cc: Vishal Verma <vishal.l.verma@intel.com>
> Cc: Dave Jiang <dave.jiang@intel.com>
> Cc: nvdimm@lists.linux.dev
> Cc: Vinod Koul <vkoul@kernel.org>
> Cc: dmaengine@vger.kernel.org
> Cc: Song Liu <song@kernel.org>
> Cc: linux-raid@vger.kernel.org
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Cc: linux-usb@vger.kernel.org
> ---
[...]
> Documentation/driver-api/md/md-cluster.rst | 2 +-
> Documentation/driver-api/md/raid5-cache.rst | 2 +-
For md bits:
Acked-by: Song Liu <song@kernel.org>
[...]
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [PATCH 2/9] Documentation: driver-api: correct spelling
2023-01-29 23:10 ` [PATCH 2/9] Documentation: driver-api: " Randy Dunlap
2023-01-30 19:11 ` Dan Williams
2023-01-30 19:45 ` Song Liu
@ 2023-01-31 9:10 ` Greg Kroah-Hartman
2 siblings, 0 replies; 16+ messages in thread
From: Greg Kroah-Hartman @ 2023-01-31 9:10 UTC (permalink / raw)
To: Randy Dunlap
Cc: linux-kernel, Jonathan Corbet, linux-doc, Mauro Carvalho Chehab,
linux-media, Dan Williams, Vishal Verma, Dave Jiang, nvdimm,
Vinod Koul, dmaengine, Song Liu, linux-raid, linux-usb
On Sun, Jan 29, 2023 at 03:10:46PM -0800, Randy Dunlap wrote:
> Correct spelling problems for Documentation/driver-api/ as reported
> by codespell.
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Jonathan Corbet <corbet@lwn.net>
> Cc: linux-doc@vger.kernel.org
> Cc: Mauro Carvalho Chehab <mchehab@kernel.org>
> Cc: linux-media@vger.kernel.org
> Cc: Dan Williams <dan.j.williams@intel.com>
> Cc: Vishal Verma <vishal.l.verma@intel.com>
> Cc: Dave Jiang <dave.jiang@intel.com>
> Cc: nvdimm@lists.linux.dev
> Cc: Vinod Koul <vkoul@kernel.org>
> Cc: dmaengine@vger.kernel.org
> Cc: Song Liu <song@kernel.org>
> Cc: linux-raid@vger.kernel.org
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Cc: linux-usb@vger.kernel.org
> ---
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [PATCH 0/9] Documentation: correct lots of spelling errors (series 2)
2023-01-29 23:10 [PATCH 0/9] Documentation: correct lots of spelling errors (series 2) Randy Dunlap
` (2 preceding siblings ...)
2023-01-29 23:10 ` [PATCH 9/9] Documentation: userspace-api: " Randy Dunlap
@ 2023-01-31 12:10 ` patchwork-bot+netdevbpf
2023-01-31 12:17 ` Paolo Abeni
2023-02-02 18:09 ` Jonathan Corbet
2023-02-14 16:57 ` (subset) " Martin K. Petersen
5 siblings, 1 reply; 16+ messages in thread
From: patchwork-bot+netdevbpf @ 2023-01-31 12:10 UTC (permalink / raw)
To: Randy Dunlap
Cc: linux-kernel, corbet, linux-doc, tj, lizefan.x, hannes, cgroups,
agk, snitzer, dm-devel, mchehab, linux-media, linux-mm,
dan.j.williams, vishal.l.verma, dave.jiang, nvdimm, vkoul,
dmaengine, song, linux-raid, gregkh, linux-usb, jdelvare, linux,
linux-hwmon, jiri, davem, edumazet, kuba, pabeni, netdev,
paulmck, frederic, quic_neeraju, josh, rcu, jejb,
martin.petersen, linux-scsi, sparclinux
Hello:
This patch was applied to netdev/net-next.git (master)
by Paolo Abeni <pabeni@redhat.com>:
On Sun, 29 Jan 2023 15:10:44 -0800 you wrote:
> Maintainers of specific kernel subsystems are only Cc-ed on their
> respective patches, not the entire series. [if all goes well]
>
> These patches are based on linux-next-20230127.
>
>
> [PATCH 1/9] Documentation: admin-guide: correct spelling
> [PATCH 2/9] Documentation: driver-api: correct spelling
> [PATCH 3/9] Documentation: hwmon: correct spelling
> [PATCH 4/9] Documentation: networking: correct spelling
> [PATCH 5/9] Documentation: RCU: correct spelling
> [PATCH 6/9] Documentation: scsi/ChangeLog*: correct spelling
> [PATCH 7/9] Documentation: scsi: correct spelling
> [PATCH 8/9] Documentation: sparc: correct spelling
> [PATCH 9/9] Documentation: userspace-api: correct spelling
>
> [...]
Here is the summary with links:
- [4/9] Documentation: networking: correct spelling
https://git.kernel.org/netdev/net-next/c/a266ef69b890
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [PATCH 0/9] Documentation: correct lots of spelling errors (series 2)
2023-01-31 12:10 ` [PATCH 0/9] Documentation: correct lots of spelling errors (series 2) patchwork-bot+netdevbpf
@ 2023-01-31 12:17 ` Paolo Abeni
0 siblings, 0 replies; 16+ messages in thread
From: Paolo Abeni @ 2023-01-31 12:17 UTC (permalink / raw)
To: patchwork-bot+netdevbpf, Randy Dunlap
Cc: linux-kernel, corbet, linux-doc, tj, lizefan.x, hannes, cgroups,
agk, snitzer, dm-devel, mchehab, linux-media, linux-mm,
dan.j.williams, vishal.l.verma, dave.jiang, nvdimm, vkoul,
dmaengine, song, linux-raid, gregkh, linux-usb, jdelvare, linux,
linux-hwmon, jiri, davem, edumazet, kuba, netdev, paulmck,
frederic, quic_neeraju, josh, rcu, jejb, martin.petersen,
linux-scsi, sparclinux
On Tue, 2023-01-31 at 12:10 +0000, patchwork-bot+netdevbpf@kernel.org
wrote:
> Hello:
>
> This patch was applied to netdev/net-next.git (master)
> by Paolo Abeni <pabeni@redhat.com>:
>
> On Sun, 29 Jan 2023 15:10:44 -0800 you wrote:
> > Maintainers of specific kernel subsystems are only Cc-ed on their
> > respective patches, not the entire series. [if all goes well]
> >
> > These patches are based on linux-next-20230127.
> >
> >
> > [PATCH 1/9] Documentation: admin-guide: correct spelling
> > [PATCH 2/9] Documentation: driver-api: correct spelling
> > [PATCH 3/9] Documentation: hwmon: correct spelling
> > [PATCH 4/9] Documentation: networking: correct spelling
> > [PATCH 5/9] Documentation: RCU: correct spelling
> > [PATCH 6/9] Documentation: scsi/ChangeLog*: correct spelling
> > [PATCH 7/9] Documentation: scsi: correct spelling
> > [PATCH 8/9] Documentation: sparc: correct spelling
> > [PATCH 9/9] Documentation: userspace-api: correct spelling
> >
> > [...]
>
> Here is the summary with links:
> - [4/9] Documentation: networking: correct spelling
> https://git.kernel.org/netdev/net-next/c/a266ef69b890
>
> You are awesome, thank you!
That is just a bot glitch. I actually applied only patch 4/9 to the
net-next tree. I hope this is not too much scarying/confusing.
Thanks,
Paolo
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [PATCH 0/9] Documentation: correct lots of spelling errors (series 2)
2023-01-29 23:10 [PATCH 0/9] Documentation: correct lots of spelling errors (series 2) Randy Dunlap
` (3 preceding siblings ...)
2023-01-31 12:10 ` [PATCH 0/9] Documentation: correct lots of spelling errors (series 2) patchwork-bot+netdevbpf
@ 2023-02-02 18:09 ` Jonathan Corbet
2023-02-02 18:33 ` Randy Dunlap
2023-02-14 16:57 ` (subset) " Martin K. Petersen
5 siblings, 1 reply; 16+ messages in thread
From: Jonathan Corbet @ 2023-02-02 18:09 UTC (permalink / raw)
To: Randy Dunlap, linux-kernel
Cc: Randy Dunlap, linux-doc, Tejun Heo, Zefan Li, Johannes Weiner,
cgroups, Alasdair Kergon, Mike Snitzer, dm-devel,
Mauro Carvalho Chehab, linux-media, linux-mm, Dan Williams,
Vishal Verma, Dave Jiang, nvdimm, Vinod Koul, dmaengine,
Song Liu, linux-raid, Greg Kroah-Hartman, linux-usb,
Jean Delvare, Guenter Roeck, linux-hwmon, Jiri Pirko,
David S. Miller, Eric Dumazet, Jakub Kicinski, Paolo Abeni,
netdev, Paul E. McKenney, Frederic Weisbecker, Neeraj Upadhyay,
Josh Triplett, rcu, James E.J. Bottomley, Martin K. Petersen,
linux-scsi, sparclinux
Randy Dunlap <rdunlap@infradead.org> writes:
> Maintainers of specific kernel subsystems are only Cc-ed on their
> respective patches, not the entire series. [if all goes well]
>
> These patches are based on linux-next-20230127.
So I've applied a bunch of these
> [PATCH 1/9] Documentation: admin-guide: correct spelling
> [PATCH 2/9] Documentation: driver-api: correct spelling
applied
> [PATCH 3/9] Documentation: hwmon: correct spelling
> [PATCH 4/9] Documentation: networking: correct spelling
> [PATCH 5/9] Documentation: RCU: correct spelling
These have been taken up elsewhere
> [PATCH 6/9] Documentation: scsi/ChangeLog*: correct spelling
> [PATCH 7/9] Documentation: scsi: correct spelling
I've left these for the SCSI folks for now. Do we *really* want to be
fixing spelling in ChangeLog files from almost 20 years ago?
> [PATCH 8/9] Documentation: sparc: correct spelling
> [PATCH 9/9] Documentation: userspace-api: correct spelling
Applied.
Thanks,
jon
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [PATCH 0/9] Documentation: correct lots of spelling errors (series 2)
2023-02-02 18:09 ` Jonathan Corbet
@ 2023-02-02 18:33 ` Randy Dunlap
2023-02-02 18:39 ` [dm-devel] " Bart Van Assche
0 siblings, 1 reply; 16+ messages in thread
From: Randy Dunlap @ 2023-02-02 18:33 UTC (permalink / raw)
To: Jonathan Corbet, linux-kernel
Cc: linux-doc, Tejun Heo, Zefan Li, Johannes Weiner, cgroups,
Alasdair Kergon, Mike Snitzer, dm-devel, Mauro Carvalho Chehab,
linux-media, linux-mm, Dan Williams, Vishal Verma, Dave Jiang,
nvdimm, Vinod Koul, dmaengine, Song Liu, linux-raid,
Greg Kroah-Hartman, linux-usb, Jean Delvare, Guenter Roeck,
linux-hwmon, Jiri Pirko, David S. Miller, Eric Dumazet,
Jakub Kicinski, Paolo Abeni, netdev, Paul E. McKenney,
Frederic Weisbecker, Neeraj Upadhyay, Josh Triplett, rcu,
James E.J. Bottomley, Martin K. Petersen, linux-scsi, sparclinux
On 2/2/23 10:09, Jonathan Corbet wrote:
> Randy Dunlap <rdunlap@infradead.org> writes:
>
>> Maintainers of specific kernel subsystems are only Cc-ed on their
>> respective patches, not the entire series. [if all goes well]
>>
>> These patches are based on linux-next-20230127.
>
> So I've applied a bunch of these
>
>> [PATCH 6/9] Documentation: scsi/ChangeLog*: correct spelling
>> [PATCH 7/9] Documentation: scsi: correct spelling
>
> I've left these for the SCSI folks for now. Do we *really* want to be
> fixing spelling in ChangeLog files from almost 20 years ago?
That's why I made it a separate patch -- so the SCSI folks can decide that...
--
~Randy
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [dm-devel] [PATCH 0/9] Documentation: correct lots of spelling errors (series 2)
2023-02-02 18:33 ` Randy Dunlap
@ 2023-02-02 18:39 ` Bart Van Assche
2023-02-02 18:46 ` Jonathan Corbet
0 siblings, 1 reply; 16+ messages in thread
From: Bart Van Assche @ 2023-02-02 18:39 UTC (permalink / raw)
To: Randy Dunlap, Jonathan Corbet, linux-kernel
Cc: nvdimm, linux-doc, Song Liu, dm-devel, netdev, Zefan Li,
sparclinux, Neeraj Upadhyay, Alasdair Kergon, Dave Jiang,
linux-scsi, Vishal Verma, Jakub Kicinski, Paolo Abeni,
James E.J. Bottomley, Guenter Roeck, linux-media, Jean Delvare,
Paul E. McKenney, Frederic Weisbecker, Mike Snitzer,
Josh Triplett, linux-raid, Tejun Heo, Jiri Pirko, cgroups,
Dan Williams, Mauro Carvalho Chehab, linux-hwmon, rcu,
Martin K. Petersen, linux-mm, Greg Kroah-Hartman, linux-usb,
Eric Dumazet, Vinod Koul, Johannes Weiner, dmaengine,
David S. Miller
On 2/2/23 10:33, Randy Dunlap wrote:
> On 2/2/23 10:09, Jonathan Corbet wrote:
>> Randy Dunlap <rdunlap@infradead.org> writes:
>>> [PATCH 6/9] Documentation: scsi/ChangeLog*: correct spelling
>>> [PATCH 7/9] Documentation: scsi: correct spelling
>>
>> I've left these for the SCSI folks for now. Do we *really* want to be
>> fixing spelling in ChangeLog files from almost 20 years ago?
>
> That's why I made it a separate patch -- so the SCSI folks can decide that...
How about removing the Documentation/scsi/ChangeLog.* files? I'm not
sure these changelogs are still useful since these duplicate information
that is already available in the output of git log ${driver_directory}.
Thanks,
Bart.
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [dm-devel] [PATCH 0/9] Documentation: correct lots of spelling errors (series 2)
2023-02-02 18:39 ` [dm-devel] " Bart Van Assche
@ 2023-02-02 18:46 ` Jonathan Corbet
2023-02-02 18:54 ` James Bottomley
0 siblings, 1 reply; 16+ messages in thread
From: Jonathan Corbet @ 2023-02-02 18:46 UTC (permalink / raw)
To: Bart Van Assche, Randy Dunlap, linux-kernel
Cc: nvdimm, linux-doc, Song Liu, dm-devel, netdev, Zefan Li,
sparclinux, Neeraj Upadhyay, Alasdair Kergon, Dave Jiang,
linux-scsi, Vishal Verma, Jakub Kicinski, Paolo Abeni,
James E.J. Bottomley, Guenter Roeck, linux-media, Jean Delvare,
Paul E. McKenney, Frederic Weisbecker, Mike Snitzer,
Josh Triplett, linux-raid, Tejun Heo, Jiri Pirko, cgroups,
Dan Williams, Mauro Carvalho Chehab, linux-hwmon, rcu,
Martin K. Petersen, linux-mm, Greg Kroah-Hartman, linux-usb,
Eric Dumazet, Vinod Koul, Johannes Weiner, dmaengine,
David S. Miller
Bart Van Assche <bvanassche@acm.org> writes:
> On 2/2/23 10:33, Randy Dunlap wrote:
>> On 2/2/23 10:09, Jonathan Corbet wrote:
>>> Randy Dunlap <rdunlap@infradead.org> writes:
>>>> [PATCH 6/9] Documentation: scsi/ChangeLog*: correct spelling
>>>> [PATCH 7/9] Documentation: scsi: correct spelling
>>>
>>> I've left these for the SCSI folks for now. Do we *really* want to be
>>> fixing spelling in ChangeLog files from almost 20 years ago?
>>
>> That's why I made it a separate patch -- so the SCSI folks can decide that...
>
> How about removing the Documentation/scsi/ChangeLog.* files? I'm not
> sure these changelogs are still useful since these duplicate information
> that is already available in the output of git log ${driver_directory}.
Actually, the information in those files mostly predates the git era, so
you won't find it that way. I *still* question their value, though...
jon
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [dm-devel] [PATCH 0/9] Documentation: correct lots of spelling errors (series 2)
2023-02-02 18:46 ` Jonathan Corbet
@ 2023-02-02 18:54 ` James Bottomley
0 siblings, 0 replies; 16+ messages in thread
From: James Bottomley @ 2023-02-02 18:54 UTC (permalink / raw)
To: Jonathan Corbet, Bart Van Assche, Randy Dunlap, linux-kernel
Cc: nvdimm, linux-doc, Song Liu, dm-devel, netdev, Zefan Li,
sparclinux, Neeraj Upadhyay, Alasdair Kergon, Dave Jiang,
linux-scsi, Vishal Verma, Jakub Kicinski, Paolo Abeni,
Guenter Roeck, linux-media, Jean Delvare, Paul E. McKenney,
Frederic Weisbecker, Mike Snitzer, Josh Triplett, linux-raid,
Tejun Heo, Jiri Pirko, cgroups, Dan Williams,
Mauro Carvalho Chehab, linux-hwmon, rcu, Martin K. Petersen,
linux-mm, Greg Kroah-Hartman, linux-usb, Eric Dumazet,
Vinod Koul, Johannes Weiner, dmaengine, David S. Miller
On Thu, 2023-02-02 at 11:46 -0700, Jonathan Corbet wrote:
> Bart Van Assche <bvanassche@acm.org> writes:
>
> > On 2/2/23 10:33, Randy Dunlap wrote:
> > > On 2/2/23 10:09, Jonathan Corbet wrote:
> > > > Randy Dunlap <rdunlap@infradead.org> writes:
> > > > > [PATCH 6/9] Documentation: scsi/ChangeLog*: correct
> > > > > spelling
> > > > > [PATCH 7/9] Documentation: scsi: correct spelling
> > > >
> > > > I've left these for the SCSI folks for now. Do we *really*
> > > > want to be
> > > > fixing spelling in ChangeLog files from almost 20 years ago?
> > >
> > > That's why I made it a separate patch -- so the SCSI folks can
> > > decide that...
> >
> > How about removing the Documentation/scsi/ChangeLog.* files? I'm
> > not sure these changelogs are still useful since these duplicate
> > information that is already available in the output of git log
> > ${driver_directory}.
>
> Actually, the information in those files mostly predates the git era,
> so you won't find it that way. I *still* question their value,
> though...
In the pre-source control days they were the answer to the GPLv2
Section 2 requirement to " carry prominent notices stating that you
changed the files and the date of any change."
If you remove the files you may run afoul of the GPLv2 Section 1
requirement to "keep intact all the notices that refer to this
License". Of course, nowadays we assume the source control does this
for us, so people rarely think of these requirements, but for files
that predate source control I think you need to consider the licence
implications.
James
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: (subset) [PATCH 0/9] Documentation: correct lots of spelling errors (series 2)
2023-01-29 23:10 [PATCH 0/9] Documentation: correct lots of spelling errors (series 2) Randy Dunlap
` (4 preceding siblings ...)
2023-02-02 18:09 ` Jonathan Corbet
@ 2023-02-14 16:57 ` Martin K. Petersen
5 siblings, 0 replies; 16+ messages in thread
From: Martin K. Petersen @ 2023-02-14 16:57 UTC (permalink / raw)
To: linux-kernel, Randy Dunlap
Cc: Martin K . Petersen, Jonathan Corbet, linux-doc, Tejun Heo,
Zefan Li, Johannes Weiner, cgroups, Alasdair Kergon,
Mike Snitzer, dm-devel, Mauro Carvalho Chehab, linux-media,
linux-mm, Dan Williams, Vishal Verma, Dave Jiang, nvdimm,
Vinod Koul, dmaengine, Song Liu, linux-raid, Greg Kroah-Hartman,
linux-usb, Jean Delvare, Guenter Roeck, linux-hwmon, Jiri Pirko,
David S. Miller, Eric Dumazet, Jakub Kicinski, Paolo Abeni,
netdev, Paul E. McKenney, Frederic Weisbecker, Neeraj Upadhyay,
Josh Triplett, rcu, James E.J. Bottomley, linux-scsi, sparclinux
On Sun, 29 Jan 2023 15:10:44 -0800, Randy Dunlap wrote:
> Maintainers of specific kernel subsystems are only Cc-ed on their
> respective patches, not the entire series. [if all goes well]
>
> These patches are based on linux-next-20230127.
>
>
> [PATCH 1/9] Documentation: admin-guide: correct spelling
> [PATCH 2/9] Documentation: driver-api: correct spelling
> [PATCH 3/9] Documentation: hwmon: correct spelling
> [PATCH 4/9] Documentation: networking: correct spelling
> [PATCH 5/9] Documentation: RCU: correct spelling
> [PATCH 6/9] Documentation: scsi/ChangeLog*: correct spelling
> [PATCH 7/9] Documentation: scsi: correct spelling
> [PATCH 8/9] Documentation: sparc: correct spelling
> [PATCH 9/9] Documentation: userspace-api: correct spelling
>
> [...]
Applied to 6.3/scsi-queue, thanks!
[6/9] Documentation: scsi/ChangeLog*: correct spelling
https://git.kernel.org/mkp/scsi/c/685d5ef436a9
[7/9] Documentation: scsi: correct spelling
https://git.kernel.org/mkp/scsi/c/cf065a7da517
--
Martin K. Petersen Oracle Linux Engineering
^ permalink raw reply [flat|nested] 16+ messages in thread
end of thread, other threads:[~2023-02-14 16:59 UTC | newest]
Thread overview: 16+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-01-29 23:10 [PATCH 0/9] Documentation: correct lots of spelling errors (series 2) Randy Dunlap
2023-01-29 23:10 ` [PATCH 1/9] Documentation: admin-guide: correct spelling Randy Dunlap
2023-01-30 9:35 ` Mukesh Ojha
2023-01-29 23:10 ` [PATCH 2/9] Documentation: driver-api: " Randy Dunlap
2023-01-30 19:11 ` Dan Williams
2023-01-30 19:45 ` Song Liu
2023-01-31 9:10 ` Greg Kroah-Hartman
2023-01-29 23:10 ` [PATCH 9/9] Documentation: userspace-api: " Randy Dunlap
2023-01-31 12:10 ` [PATCH 0/9] Documentation: correct lots of spelling errors (series 2) patchwork-bot+netdevbpf
2023-01-31 12:17 ` Paolo Abeni
2023-02-02 18:09 ` Jonathan Corbet
2023-02-02 18:33 ` Randy Dunlap
2023-02-02 18:39 ` [dm-devel] " Bart Van Assche
2023-02-02 18:46 ` Jonathan Corbet
2023-02-02 18:54 ` James Bottomley
2023-02-14 16:57 ` (subset) " Martin K. Petersen
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).