mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Otavio Salvador <otavio@ossystems.com.br>
To: linux-kernel@vger.kernel.org
Cc: Otavio Salvador <otavio@ossystems.com.br>,
	Evgeniy Polyakov <zbr@ioremap.net>
Subject: [PATCH 1/2] w1: Fix a typo in 'hardware' word
Date: Sun, 17 Jun 2012 12:17:31 -0300	[thread overview]
Message-ID: <1339946252-21019-1-git-send-email-otavio@ossystems.com.br> (raw)

Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Cc: Evgeniy Polyakov <zbr@ioremap.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


             reply	other threads:[~2012-06-17 15:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-17 15:17 Otavio Salvador [this message]
2012-06-17 15:17 ` [PATCH 2/2] pinctrl: pinctrl-mxs: fix implicit declaration of free() Otavio Salvador
2012-06-18  6:04   ` Linus Walleij
2012-06-18 12:18     ` Otavio Salvador
2012-06-18 12:27     ` devendra.aaru
2012-06-17 22:01 ` [PATCH 1/2] w1: Fix a typo in 'hardware' word Evgeniy Polyakov
2012-06-17 23:49   ` GregKH
  -- strict thread matches above, loose matches on Subject: below --
2012-06-17  3:06 Otavio Salvador

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1339946252-21019-1-git-send-email-otavio@ossystems.com.br \
    --to=otavio@ossystems.com.br \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zbr@ioremap.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®