linux-kernel - [PATCH] Fix a typo in the vgaarbiter Documentation

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 for Android: free password hash cracker in your pocket

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

Date:	Thu, 10 Dec 2009 13:55:48 +0100
From:	Detlef Riekenberg <wine.dev@....de>
To:	linux-kernel@...r.kernel.org,
	Jesse Barnes <jbarnes@...tuousgeek.org>
Cc:	Tiago Vignatti <tiago.vignatti@...ia.com>
Subject: [PATCH] Fix a typo in the vgaarbiter Documentation

Hi.

I detected a typo, while reading "Documentation/vgaarbiter.txt".

Please CC me on any reply. Thanks

-- 
By by ... Detlef



>>From 84db53ffacb278312de6e374928247c360dcbced Mon Sep 17 00:00:00 2001
From: Detlef Riekenberg <wine.dev@....de>
Date: Thu, 10 Dec 2009 13:39:15 +0100
Subject: [PATCH] Fix a typo in the vgaarbiter Documentation

Signed-off-by: Detlef Riekenberg <wine.dev@....de>
---
 Documentation/vgaarbiter.txt |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/Documentation/vgaarbiter.txt b/Documentation/vgaarbiter.txt
index 987f9b0..43a9b06 100644
--- a/Documentation/vgaarbiter.txt
+++ b/Documentation/vgaarbiter.txt
@@ -103,7 +103,7 @@ I.2 libpciaccess
 ----------------
 
 To use the vga arbiter char device it was implemented an API inside the
-libpciaccess library. One fieldd was added to struct pci_device (each
device
+libpciaccess library. One field was added to struct pci_device (each
device
 on the system):
 
     /* the type of resource decoded by the device */
-- 
1.5.4.3




--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/