linux-kernel - [PATCH] driver core: auxiliary bus: Spelling s/pecific/specific/

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <f232a09c377cbe11c81b4ab69d4e7bf016e746c8.1730282860.git.geert+renesas@glider.be>
Date: Wed, 30 Oct 2024 11:10:22 +0100
From: Geert Uytterhoeven <geert+renesas@...der.be>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Dave Ertman <david.m.ertman@...el.com>,
	Ira Weiny <ira.weiny@...el.com>,
	"Rafael J . Wysocki" <rafael@...nel.org>,
	Dan Williams <dan.j.williams@...el.com>,
	Leon Romanovsky <leon@...nel.org>,
	Shiraz Saleem <shiraz.saleem@...el.com>,
	Kiran Patil <kiran.patil@...el.com>,
	Martin Habets <mhabets@...arflare.com>
Cc: linux-kernel@...r.kernel.org,
	Geert Uytterhoeven <geert+renesas@...der.be>
Subject: [PATCH] driver core: auxiliary bus: Spelling s/pecific/specific/

Fix a misspelling of the word "specific".

Fixes: 7de3697e9cbd4bd3 ("Add auxiliary bus support")
Fixes: e1b5186810cc7d4e ("Documentation/auxiliary_bus: Move the text into the code")
Signed-off-by: Geert Uytterhoeven <geert+renesas@...der.be>
---
The documentation was moved and reformatted, so I used two Fixes tags.
---
 drivers/base/auxiliary.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/base/auxiliary.c b/drivers/base/auxiliary.c
index 69b7c93613d6dc00..afa4df4c5a3f371b 100644
--- a/drivers/base/auxiliary.c
+++ b/drivers/base/auxiliary.c
@@ -92,7 +92,7 @@
  * Auxiliary devices are created and registered by a subsystem-level core
  * device that needs to break up its functionality into smaller fragments. One
  * way to extend the scope of an auxiliary_device is to encapsulate it within a
- * domain- pecific structure defined by the parent device. This structure
+ * domain-specific structure defined by the parent device. This structure
  * contains the auxiliary_device and any associated shared data/callbacks
  * needed to establish the connection with the parent.
  *
-- 
2.34.1