linux-kernel - [PATCH 1/2] w1: Fix a typo in 'hardware' word

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: <1339902416-19299-1-git-send-email-otavio@ossystems.com.br>
Date:	Sun, 17 Jun 2012 00:06:54 -0300
From:	Otavio Salvador <otavio@...ystems.com.br>
To:	linux-kernel@...r.kernel.org
Cc:	Otavio Salvador <otavio@...ystems.com.br>,
	Evgeniy Polyakov <zbr@...emap.net>
Subject: [PATCH 1/2] w1: Fix a typo in 'hardware' word

Signed-off-by: Otavio Salvador <otavio@...ystems.com.br>
Cc: Evgeniy Polyakov <zbr@...emap.net>
---
 drivers/w1/w1_int.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/w1/w1_int.c b/drivers/w1/w1_int.c
index 6828835..afa5f5d 100644
--- a/drivers/w1/w1_int.c
+++ b/drivers/w1/w1_int.c
@@ -117,7 +117,7 @@ int w1_add_master_device(struct w1_bus_master *master)
 		return(-EINVAL);
         }
 	/* While it would be electrically possible to make a device that
-	 * generated a strong pullup in bit bang mode, only hardare that
+	 * generated a strong pullup in bit bang mode, only hardware that
 	 * controls 1-wire time frames are even expected to support a strong
 	 * pullup.  w1_io.c would need to support calling set_pullup before
 	 * the last write_bit operation of a w1_write_8 which it currently
-- 
1.7.10

--
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/