From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org
Subject: [PATCH] bitops updates
Date: Wed, 16 Jul 2014 10:37:49 +0200 [thread overview]
Message-ID: <1405499873-6385-1-git-send-email-s.hauer@pengutronix.de> (raw)
This cleans up the architecture specific arch/*/include/asm/bitops.h
files. We have many variants of the same file in the tree, many
missing some includes or defines. With this series we consistently
use the same version.
Sascha
----------------------------------------------------------------
Sascha Hauer (4):
X86: Move BITS_PER_LONG definition to types.h
consistently use the same bitops.h file
ppc: Use generic find_*_bit functions
ppc: Add missing __ffs implementation
arch/blackfin/Kconfig | 1 +
arch/blackfin/include/asm/bitops.h | 361 ++-----------------------------------
arch/mips/include/asm/bitops.h | 26 +--
arch/nios2/Kconfig | 1 +
arch/nios2/include/asm/bitops.h | 32 +++-
arch/openrisc/Kconfig | 1 +
arch/openrisc/include/asm/bitops.h | 29 ++-
arch/ppc/Kconfig | 1 +
arch/ppc/include/asm/bitops.h | 49 +----
arch/sandbox/include/asm/bitops.h | 25 ++-
arch/x86/include/asm/bitops.h | 32 ++--
arch/x86/include/asm/types.h | 2 +
12 files changed, 128 insertions(+), 432 deletions(-)
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2014-07-16 8:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-16 8:37 Sascha Hauer [this message]
2014-07-16 8:37 ` [PATCH 1/4] X86: Move BITS_PER_LONG definition to types.h Sascha Hauer
2014-07-16 8:37 ` [PATCH 2/4] consistently use the same bitops.h file Sascha Hauer
2014-07-16 8:37 ` [PATCH 3/4] ppc: Use generic find_*_bit functions Sascha Hauer
2014-07-16 8:37 ` [PATCH 4/4] ppc: Add missing __ffs implementation Sascha Hauer
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=1405499873-6385-1-git-send-email-s.hauer@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox