From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Anton Vorontsov <avorontsov@ru.mvista.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Jonas Aaberg <jonas.aberg@stericsson.com>,
Mian Yousaf Kaukab <mian.yousaf.kaukab@stericsson.com>,
Lee Jones <lee.jones@linaro.org>,
Samuel Ortiz <sameo@linux.intel.com>
Subject: linux-next: manual merge of the battery tree with the mfd tree
Date: Wed, 6 Feb 2013 14:31:20 +1100 [thread overview]
Message-ID: <20130206143120.73c66ac3eadced968f9dd2d5@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1656 bytes --]
Hi Anton,
Today's linux-next merge of the battery tree got a conflict in
include/linux/mfd/abx500/ab8500.h between commit 1d843a6c8c20 ("mfd:
ab8500-core: Allow the possibility to dump all AB8500 registers") from
the mfd tree and commit 0ed5107fa860 ("ab8500-charger: Do not touch
VBUSOVV bits") from the battery tree.
I fixed it up (see below) and can carry the fix as necessary (no action
is required).
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
diff --cc include/linux/mfd/abx500/ab8500.h
index fa7173d,b9a6a84..0000000
--- a/include/linux/mfd/abx500/ab8500.h
+++ b/include/linux/mfd/abx500/ab8500.h
@@@ -345,12 -346,23 +350,32 @@@ static inline int is_ab8500_2p0(struct
return (is_ab8500(ab) && (ab->chip_id == AB8500_CUT2P0));
}
+ static inline int is_ab8505_1p0_or_earlier(struct ab8500 *ab)
+ {
+ return (is_ab8505(ab) && (ab->chip_id <= AB8500_CUT1P0));
+ }
+
+ static inline int is_ab8505_2p0(struct ab8500 *ab)
+ {
+ return (is_ab8505(ab) && (ab->chip_id == AB8500_CUT2P0));
+ }
+
+ static inline int is_ab9540_1p0_or_earlier(struct ab8500 *ab)
+ {
+ return (is_ab9540(ab) && (ab->chip_id <= AB8500_CUT1P0));
+ }
+
+ static inline int is_ab9540_2p0(struct ab8500 *ab)
+ {
+ return (is_ab9540(ab) && (ab->chip_id == AB8500_CUT2P0));
+ }
++
+#ifdef CONFIG_AB8500_DEBUG
+void ab8500_dump_all_banks(struct device *dev);
+void ab8500_debug_register_interrupt(int line);
+#else
+static inline void ab8500_dump_all_banks(struct device *dev) {}
+static inline void ab8500_debug_register_interrupt(int line) {}
+#endif
+
#endif /* MFD_AB8500_H */
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2013-02-06 3:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-06 3:31 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-21 2:33 Stephen Rothwell
2019-06-28 3:45 Stephen Rothwell
2019-06-28 15:35 ` Sebastian Reichel
2012-09-21 3:15 Stephen Rothwell
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=20130206143120.73c66ac3eadced968f9dd2d5@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=avorontsov@ru.mvista.com \
--cc=jonas.aberg@stericsson.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mian.yousaf.kaukab@stericsson.com \
--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
all inboxes | Powered by JetHome®