From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Linus Walleij <linus.walleij@linaro•org>,
Thomas Gleixner <tglx@linutronix•de>, Ingo Molnar <mingo@elte•hu>,
"H. Peter Anvin" <hpa@zytor•com>,
Peter Zijlstra <peterz@infradead•org>
Cc: Linux-Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Lukas Wunner <lukas@wunner•de>, Andi Kleen <ak@linux•intel.com>
Subject: linux-next: manual merge of the gpio tree with the tip tree
Date: Thu, 2 Nov 2017 15:59:52 +1100 [thread overview]
Message-ID: <20171102155952.56d90a49@canb.auug.org.au> (raw)
Hi Linus,
Today's linux-next merge of the gpio tree got a conflict in:
include/linux/bitops.h
between commit:
cbe96375025e ("bitops: Add clear/set_bit32() to linux/bitops.h")
from the tip tree and commit:
5307e2ad69ab ("bitops: Introduce assign_bit()")
from the gpio tree.
I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging. You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.
--
Cheers,
Stephen Rothwell
diff --cc include/linux/bitops.h
index 15a5bcfcd0a2,9a874deee6e2..000000000000
--- a/include/linux/bitops.h
+++ b/include/linux/bitops.h
@@@ -227,32 -227,30 +227,56 @@@ static inline unsigned long __ffs64(u6
return __ffs((unsigned long)word);
}
+/*
+ * clear_bit32 - Clear a bit in memory for u32 array
+ * @nr: Bit to clear
+ * @addr: u32 * address of bitmap
+ *
+ * Same as clear_bit, but avoids needing casts for u32 arrays.
+ */
+
+static __always_inline void clear_bit32(long nr, volatile u32 *addr)
+{
+ clear_bit(nr, (volatile unsigned long *)addr);
+}
+
+/*
+ * set_bit32 - Set a bit in memory for u32 array
+ * @nr: Bit to clear
+ * @addr: u32 * address of bitmap
+ *
+ * Same as set_bit, but avoids needing casts for u32 arrays.
+ */
+
+static __always_inline void set_bit32(long nr, volatile u32 *addr)
+{
+ set_bit(nr, (volatile unsigned long *)addr);
+}
+
+ /**
+ * assign_bit - Assign value to a bit in memory
+ * @nr: the bit to set
+ * @addr: the address to start counting from
+ * @value: the value to assign
+ */
+ static __always_inline void assign_bit(long nr, volatile unsigned long *addr,
+ bool value)
+ {
+ if (value)
+ set_bit(nr, addr);
+ else
+ clear_bit(nr, addr);
+ }
+
+ static __always_inline void __assign_bit(long nr, volatile unsigned long *addr,
+ bool value)
+ {
+ if (value)
+ __set_bit(nr, addr);
+ else
+ __clear_bit(nr, addr);
+ }
+
#ifdef __KERNEL__
#ifndef set_mask_bits
next reply other threads:[~2017-11-02 4:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-02 4:59 Stephen Rothwell [this message]
2017-11-02 8:06 ` linux-next: manual merge of the gpio tree with the tip tree Peter Zijlstra
2017-11-02 8:26 ` Stephen Rothwell
2017-11-02 8:38 ` Peter Zijlstra
-- strict thread matches above, loose matches on Subject: below --
2016-03-02 4:27 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=20171102155952.56d90a49@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=ak@linux$(echo .)intel.com \
--cc=hpa@zytor$(echo .)com \
--cc=linus.walleij@linaro$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=lukas@wunner$(echo .)de \
--cc=mingo@elte$(echo .)hu \
--cc=peterz@infradead$(echo .)org \
--cc=tglx@linutronix$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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