From: Andrew Jeffery <andrew@aj.id.au>
To: linux@roeck-us.net, linux-hwmon@vger.kernel.org
Cc: Andrew Jeffery <andrew@aj.id.au>,
jdelvare@suse.com, linux-kernel@vger.kernel.org, joel@jms.id.au,
openbmc@lists.ozlabs.org, msbarth@linux.vnet.ibm.com,
mspinler@linux.vnet.ibm.com
Subject: [RFC PATCH 1/4] hwmon: pmbus: Disable build of non-max31785 drivers
Date: Mon, 10 Jul 2017 23:26:15 +0930 [thread overview]
Message-ID: <20170710135618.13661-2-andrew@aj.id.au> (raw)
In-Reply-To: <20170710135618.13661-1-andrew@aj.id.au>
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
---
Later patches make incompatible changes to struct pmbus_driver_info, so this
serves to keep the following patches buildable under otherwise incompatible
configurations. It is a junk patch that won't be present in a non-RFC series.
drivers/hwmon/pmbus/Makefile | 24 ++++++++++++------------
1 file changed, 12 insertions(+), 12 deletions(-)
diff --git a/drivers/hwmon/pmbus/Makefile b/drivers/hwmon/pmbus/Makefile
index 562132054aaf..24ff7ee7f8bb 100644
--- a/drivers/hwmon/pmbus/Makefile
+++ b/drivers/hwmon/pmbus/Makefile
@@ -4,15 +4,15 @@
obj-$(CONFIG_PMBUS) += pmbus_core.o
obj-$(CONFIG_SENSORS_PMBUS) += pmbus.o
-obj-$(CONFIG_SENSORS_ADM1275) += adm1275.o
-obj-$(CONFIG_SENSORS_LM25066) += lm25066.o
-obj-$(CONFIG_SENSORS_LTC2978) += ltc2978.o
-obj-$(CONFIG_SENSORS_LTC3815) += ltc3815.o
-obj-$(CONFIG_SENSORS_MAX16064) += max16064.o
-obj-$(CONFIG_SENSORS_MAX20751) += max20751.o
-obj-$(CONFIG_SENSORS_MAX34440) += max34440.o
-obj-$(CONFIG_SENSORS_MAX8688) += max8688.o
-obj-$(CONFIG_SENSORS_TPS40422) += tps40422.o
-obj-$(CONFIG_SENSORS_UCD9000) += ucd9000.o
-obj-$(CONFIG_SENSORS_UCD9200) += ucd9200.o
-obj-$(CONFIG_SENSORS_ZL6100) += zl6100.o
+# obj-$(CONFIG_SENSORS_ADM1275) += adm1275.o
+# obj-$(CONFIG_SENSORS_LM25066) += lm25066.o
+# obj-$(CONFIG_SENSORS_LTC2978) += ltc2978.o
+# obj-$(CONFIG_SENSORS_LTC3815) += ltc3815.o
+# obj-$(CONFIG_SENSORS_MAX16064) += max16064.o
+# obj-$(CONFIG_SENSORS_MAX20751) += max20751.o
+# obj-$(CONFIG_SENSORS_MAX34440) += max34440.o
+# obj-$(CONFIG_SENSORS_MAX8688) += max8688.o
+# obj-$(CONFIG_SENSORS_TPS40422) += tps40422.o
+# obj-$(CONFIG_SENSORS_UCD9000) += ucd9000.o
+# obj-$(CONFIG_SENSORS_UCD9200) += ucd9200.o
+# obj-$(CONFIG_SENSORS_ZL6100) += zl6100.o
--
2.11.0
next prev parent reply other threads:[~2017-07-10 13:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-10 13:56 [RFC PATCH 0/4] pmbus: Expand fan support and add MAX31785 driver Andrew Jeffery
2017-07-10 13:56 ` Andrew Jeffery [this message]
2017-07-10 13:56 ` [RFC PATCH 2/4] pmbus: Add fan configuration support Andrew Jeffery
2017-07-11 13:40 ` Guenter Roeck
2017-07-12 0:39 ` Andrew Jeffery
2017-07-12 0:39 ` Andrew Jeffery
2017-07-12 3:43 ` Guenter Roeck
2017-07-12 7:01 ` Andrew Jeffery
2017-07-12 7:01 ` Andrew Jeffery
2017-07-12 15:10 ` Guenter Roeck
2017-07-10 13:56 ` [RFC PATCH 3/4] pmbus: Allow dynamic fan coefficient values Andrew Jeffery
2017-07-11 13:31 ` Guenter Roeck
2017-07-12 1:20 ` Andrew Jeffery
2017-07-12 1:20 ` Andrew Jeffery
2017-07-12 3:20 ` Guenter Roeck
2017-07-10 13:56 ` [RFC PATCH 4/4] pmbus: Add MAX31785 driver Andrew Jeffery
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=20170710135618.13661-2-andrew@aj.id.au \
--to=andrew@aj.id.au \
--cc=jdelvare@suse.com \
--cc=joel@jms.id.au \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=msbarth@linux.vnet.ibm.com \
--cc=mspinler@linux.vnet.ibm.com \
--cc=openbmc@lists.ozlabs.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 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.