From: Sebastian Reichel <sre@kernel.org>
To: Sebastian Reichel <sre@kernel.org>,
Richard Purdie <rpurdie@rpsys.net>,
Jacek Anaszewski <jacek.anaszewski@gmail.com>,
Pavel Machek <pavel@ucw.cz>, Lee Jones <lee.jones@linaro.org>
Cc: Tony Lindgren <tony@atomide.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCHv3 1/2] mfd: cpcap: Add missing include dependencies
Date: Fri, 24 Mar 2017 09:47:31 +0100 [thread overview]
Message-ID: <20170324084732.31255-1-sre@kernel.org> (raw)
This fixes compilation for files, that try to include the
cpcap header in alphabetically sorted #include lists.
Acked-by: Pavel Machek <pavel@ucw.cz>
Acked-by: Tony Lindgren <tony@atomide.com>
Signed-off-by: Sebastian Reichel <sre@kernel.org>
---
Changes since PATCHv2:
- Add Acked-by from Tony & Pavel
---
include/linux/mfd/motorola-cpcap.h | 3 +++
1 file changed, 3 insertions(+)
diff --git a/include/linux/mfd/motorola-cpcap.h b/include/linux/mfd/motorola-cpcap.h
index 793aa695faa0..aefc49cb7ba9 100644
--- a/include/linux/mfd/motorola-cpcap.h
+++ b/include/linux/mfd/motorola-cpcap.h
@@ -14,6 +14,9 @@
* published by the Free Software Foundation.
*/
+#include <linux/device.h>
+#include <linux/regmap.h>
+
#define CPCAP_VENDOR_ST 0
#define CPCAP_VENDOR_TI 1
--
2.11.0
next reply other threads:[~2017-03-24 8:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-24 8:47 Sebastian Reichel [this message]
2017-03-24 8:47 ` [PATCHv3 2/2] leds: cpcap: new driver Sebastian Reichel
2017-03-29 19:12 ` Jacek Anaszewski
2017-03-29 21:38 ` Sebastian Reichel
2017-03-24 20:44 ` [PATCHv3 1/2] mfd: cpcap: Add missing include dependencies Jacek Anaszewski
2017-03-27 14:26 ` Lee Jones
2017-03-27 18:38 ` Jacek Anaszewski
2017-03-28 8:16 ` Lee Jones
2017-03-28 8:13 ` [GIT PULL] Immutable branch between MFD and LEDS due for the v4.12 merge window Lee Jones
2017-03-28 19:37 ` Jacek Anaszewski
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=20170324084732.31255-1-sre@kernel.org \
--to=sre@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jacek.anaszewski@gmail.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pavel@ucw.cz \
--cc=robh+dt@kernel.org \
--cc=rpurdie@rpsys.net \
--cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).