summaryrefslogtreecommitdiff
path: root/Documentation/driver-api/eisa.rst
diff options
context:
space:
mode:
authorMarneni PoornaChandu <poornachandumarneni@gmail.com>2025-09-18 06:04:30 +0800
committerJonathan Corbet <corbet@lwn.net>2025-09-18 10:40:46 -0600
commit395107a7c91aafef8eb8ffee574b43cc7cce34be (patch)
treeda55530242059cc4d1827e03f83f5f634895f0dd /Documentation/driver-api/eisa.rst
parent4eb018bd15881504351c44f0d3d7287c88ef161f (diff)
docs: driver-api: fix spelling of "buses".
Replace incorrect plural form "busses" with "buses" in multiple documentation files under "Documentation/driver-api". Signed-off-by: Marneni PoornaChandu <Poornachandumarneni@gmail.com> Signed-off-by: Jonathan Corbet <corbet@lwn.net> Message-ID: <20250917220430.5815-1-Poornachandumarneni@gmail.com>
Diffstat (limited to 'Documentation/driver-api/eisa.rst')
-rw-r--r--Documentation/driver-api/eisa.rst6
1 files changed, 3 insertions, 3 deletions
diff --git a/Documentation/driver-api/eisa.rst b/Documentation/driver-api/eisa.rst
index b33ebe1ec9ed..3563e5f7e98d 100644
--- a/Documentation/driver-api/eisa.rst
+++ b/Documentation/driver-api/eisa.rst
@@ -8,9 +8,9 @@ This document groups random notes about porting EISA drivers to the
new EISA/sysfs API.
Starting from version 2.5.59, the EISA bus is almost given the same
-status as other much more mainstream busses such as PCI or USB. This
+status as other much more mainstream buses such as PCI or USB. This
has been possible through sysfs, which defines a nice enough set of
-abstractions to manage busses, devices and drivers.
+abstractions to manage buses, devices and drivers.
Although the new API is quite simple to use, converting existing
drivers to the new infrastructure is not an easy task (mostly because
@@ -205,7 +205,7 @@ Random notes
Converting an EISA driver to the new API mostly involves *deleting*
code (since probing is now in the core EISA code). Unfortunately, most
drivers share their probing routine between ISA, and EISA. Special
-care must be taken when ripping out the EISA code, so other busses
+care must be taken when ripping out the EISA code, so other buses
won't suffer from these surgical strikes...
You *must not* expect any EISA device to be detected when returning