From: Axel Lin <axel.lin@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: Lee Jones <lee.jones@linaro.org>,
Samuel Ortiz <sameo@linux.intel.com>,
Linus Walleij <linus.walleij@linaro.org>
Subject: [PATCH] mfd: Remove config AB8500_I2C_CORE Kconfig entry
Date: Tue, 29 May 2012 14:19:00 +0800 [thread overview]
Message-ID: <1338272340.3127.1.camel@phoenix> (raw)
config AB8500_I2C_CORE is not used after commit d28f1db
"mfd: Remove confusing ab8500-i2c file and merge into ab8500-core".
Thus remove it.
Signed-off-by: Axel Lin <axel.lin@gmail.com>
---
drivers/mfd/Kconfig | 10 ----------
1 file changed, 10 deletions(-)
diff --git a/drivers/mfd/Kconfig b/drivers/mfd/Kconfig
index e129c82..170072e 100644
--- a/drivers/mfd/Kconfig
+++ b/drivers/mfd/Kconfig
@@ -703,16 +703,6 @@ config AB8500_CORE
the irq_chip parts for handling the Mixed Signal chip events.
This chip embeds various other multimedia funtionalities as well.
-config AB8500_I2C_CORE
- bool "AB8500 register access via PRCMU I2C"
- depends on AB8500_CORE && MFD_DB8500_PRCMU
- default y
- help
- This enables register access to the AB8500 chip via PRCMU I2C.
- The AB8500 chip can be accessed via SPI or I2C. On DB8500 hardware
- the I2C bus is connected to the Power Reset
- and Mangagement Unit, PRCMU.
-
config AB8500_DEBUG
bool "Enable debug info via debugfs"
depends on AB8500_CORE && DEBUG_FS
--
1.7.9.5
next reply other threads:[~2012-05-29 6:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-29 6:19 Axel Lin [this message]
2012-05-29 7:38 ` [PATCH] mfd: Remove config AB8500_I2C_CORE Kconfig entry Lee Jones
2012-05-29 7:53 ` Axel Lin
2012-05-29 8:29 ` Lee Jones
2012-05-29 9:15 ` Samuel Ortiz
2012-05-29 9:27 ` Lee Jones
2012-05-29 10:52 ` Samuel Ortiz
2012-05-29 15:06 ` Lee Jones
2012-05-29 15:27 ` Samuel Ortiz
2012-05-29 15:37 ` Lee Jones
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=1338272340.3127.1.camel@phoenix \
--to=axel.lin@gmail.com \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sameo@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox