From: bunk@stusta.de (Adrian Bunk)
To: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
Cc: sensors@stimpy.netroedge.com, linux-kernel@vger.kernel.org
Subject: [2.6 patch] make W1_DS9490_BRIDGE available
Date: Thu, 19 May 2005 06:25:23 +0000 [thread overview]
Message-ID: <20041122155102.GD19419@stusta.de> (raw)
It seems noone noted that due to a typo, the W1_DS9490_BRIDGE option
didn't have any effect.
Signed-off-by: Adrian Bunk <bunk@stusta.de>
--- linux-2.6.10-rc2-mm3-full/drivers/w1/Kconfig.old 2004-11-22 14:34:13.000000000 +0100
+++ linux-2.6.10-rc2-mm3-full/drivers/w1/Kconfig 2004-11-22 14:34:21.000000000 +0100
@@ -30,7 +30,7 @@
This support is also available as a module. If so, the module
will be called ds9490r.ko.
-config W1_DS9490R_BRIDGE
+config W1_DS9490_BRIDGE
tristate "DS9490R USB <-> W1 transport layer for 1-wire"
depends on W1_DS9490
help
WARNING: multiple messages have this Message-ID (diff)
From: Adrian Bunk <bunk@stusta.de>
To: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
Cc: sensors@stimpy.netroedge.com, linux-kernel@vger.kernel.org
Subject: [2.6 patch] make W1_DS9490_BRIDGE available
Date: Mon, 22 Nov 2004 16:51:02 +0100 [thread overview]
Message-ID: <20041122155102.GD19419@stusta.de> (raw)
It seems noone noted that due to a typo, the W1_DS9490_BRIDGE option
didn't have any effect.
Signed-off-by: Adrian Bunk <bunk@stusta.de>
--- linux-2.6.10-rc2-mm3-full/drivers/w1/Kconfig.old 2004-11-22 14:34:13.000000000 +0100
+++ linux-2.6.10-rc2-mm3-full/drivers/w1/Kconfig 2004-11-22 14:34:21.000000000 +0100
@@ -30,7 +30,7 @@
This support is also available as a module. If so, the module
will be called ds9490r.ko.
-config W1_DS9490R_BRIDGE
+config W1_DS9490_BRIDGE
tristate "DS9490R USB <-> W1 transport layer for 1-wire"
depends on W1_DS9490
help
next reply other threads:[~2005-05-19 6:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-22 15:51 Adrian Bunk [this message]
2005-05-19 6:25 ` [2.6 patch] make W1_DS9490_BRIDGE available Adrian Bunk
2004-11-22 16:20 ` Evgeniy Polyakov
2005-05-19 6:25 ` Evgeniy Polyakov
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=20041122155102.GD19419@stusta.de \
--to=bunk@stusta.de \
--cc=johnpol@2ka.mipt.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=sensors@stimpy.netroedge.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.