From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: jic23@kernel.org, khali@linux-fr.org
Cc: linux-iio@vger.kernel.org, linux-i2c@vger.kernel.org,
ktsai@capellamicro.com,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Subject: [RFC Patch v0 2/3] i2c-smbus: Allow building with I2C_HELPER_AUTO support
Date: Wed, 26 Mar 2014 17:42:11 -0700 [thread overview]
Message-ID: <1395880932-19124-2-git-send-email-srinivas.pandruvada@linux.intel.com> (raw)
In-Reply-To: <1395880932-19124-1-git-send-email-srinivas.pandruvada@linux.intel.com>
Currentlty the config is conditional on !I2C_HELPER_AUTO.
I don't know their dependency, but without this we can't build.
Signed-off-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
---
drivers/i2c/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/i2c/Kconfig b/drivers/i2c/Kconfig
index 7b7ea32..212ed73 100644
--- a/drivers/i2c/Kconfig
+++ b/drivers/i2c/Kconfig
@@ -74,7 +74,7 @@ config I2C_HELPER_AUTO
In doubt, say Y.
config I2C_SMBUS
- tristate "SMBus-specific protocols" if !I2C_HELPER_AUTO
+ tristate "SMBus-specific protocols"
help
Say Y here if you want support for SMBus extensions to the I2C
specification. At the moment, the only supported extension is
--
1.8.3.2
next prev parent reply other threads:[~2014-03-27 0:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-27 0:42 [RFC Patch v0 1/3] i2c-smbus: Add poll interface for smbus alert Srinivas Pandruvada
2014-03-27 0:42 ` Srinivas Pandruvada [this message]
2014-03-27 6:57 ` [RFC Patch v0 2/3] i2c-smbus: Allow building with I2C_HELPER_AUTO support Jean Delvare
2014-03-27 15:26 ` Srinivas Pandruvada
2014-03-27 0:42 ` [RFC Patch v0 3/3] iio: Capella cm3218x: smbus alert processing Srinivas Pandruvada
2014-03-27 7:44 ` [RFC Patch v0 1/3] i2c-smbus: Add poll interface for smbus alert Jean Delvare
2014-03-27 15:39 ` Srinivas Pandruvada
2014-03-27 17:34 ` Jonathan Cameron
2014-03-27 21:50 ` Srinivas Pandruvada
2014-03-29 10:15 ` Jonathan Cameron
2014-03-31 15:26 ` Srinivas Pandruvada
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=1395880932-19124-2-git-send-email-srinivas.pandruvada@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=jic23@kernel.org \
--cc=khali@linux-fr.org \
--cc=ktsai@capellamicro.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
/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