From: Hans-Christian Egtvedt <hans-christian.egtvedt@atmel.com>
To: Akinobu Mita <akinobu.mita@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
akpm@linux-foundation.org, arnd@arndb.de,
Russell King <linux@arm.linux.org.uk>,
linux-arm-kernel@lists.infradead.org,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
linux390@de.ibm.com, linux-s390@vger.kernel.org,
Geert Uytterhoeven <geert@linux-m68k.org>,
linux-m68k@vger.kernel.org, Greg Ungerer <gerg@uclinux.org>
Subject: Re: [PATCH 1/6] arch: add #define for each of optimized find bitops
Date: Tue, 26 Apr 2011 14:23:20 +0200 [thread overview]
Message-ID: <1303820600.3125.13.camel@hcegtvedt> (raw)
In-Reply-To: <1303638677-11211-2-git-send-email-akinobu.mita@gmail.com>
On Sun, 2011-04-24 at 18:51 +0900, Akinobu Mita wrote:
> The style that we normally use in asm-generic is to test the macro itself
> for existence, so in asm-generic, do:
>
> #ifndef find_next_zero_bit_le
> extern unsigned long find_next_zero_bit_le(const void *addr,
> unsigned long size, unsigned long offset);
> #endif
>
> and in the architectures, write
>
> static inline unsigned long find_next_zero_bit_le(const void *addr,
> unsigned long size, unsigned long offset)
> #define find_next_zero_bit_le find_next_zero_bit_le
>
> This adds the #define for each of the optimized find bitops in the
> architectures.
>
> Suggested-by: Arnd Bergmann <arnd@arndb.de>
> Signed-off-by: Akinobu Mita <akinobu.mita@gmail.com>
> Cc: Russell King <linux@arm.linux.org.uk>
> Cc: linux-arm-kernel@lists.infradead.org
> Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>
> Cc: Heiko Carstens <heiko.carstens@de.ibm.com>
> Cc: linux390@de.ibm.com
> Cc: linux-s390@vger.kernel.org
> Cc: Hans-Christian Egtvedt <hans-christian.egtvedt@atmel.com>
> Cc: Geert Uytterhoeven <geert@linux-m68k.org>
> Cc: linux-m68k@lists.linux-m68k.org
> Cc: Greg Ungerer <gerg@uclinux.org>
For the arch/avr32/include/asm/bitops.h changes.
Acked-by: Hans-Christian Egtvedt <hans-christian.egtvedt@atmel.com>
--
Hans-Christian Egtvedt
next prev parent reply other threads:[~2011-04-26 12:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-24 9:51 [PATCH 0/6] remove CONFIG_GENERIC_FIND_{NEXT_BIT,BIT_LE,LAST_BIT} Akinobu Mita
2011-04-24 9:51 ` [PATCH 1/6] arch: add #define for each of optimized find bitops Akinobu Mita
2011-04-24 9:51 ` Akinobu Mita
2011-04-26 12:23 ` Hans-Christian Egtvedt [this message]
2011-04-26 12:23 ` Hans-Christian Egtvedt
2011-04-24 9:51 ` [PATCH 2/6] bitops: add #ifndef for each of " Akinobu Mita
2011-04-24 9:51 ` Akinobu Mita
2011-04-24 9:51 ` [PATCH 3/6] arch: remove CONFIG_GENERIC_FIND_{NEXT_BIT,BIT_LE,LAST_BIT} Akinobu Mita
2011-04-24 9:51 ` Akinobu Mita
2011-04-24 9:51 ` [PATCH 4/6] arm: use asm-generic/bitops/le.h Akinobu Mita
2011-04-24 9:51 ` [PATCH 5/6] s390: " Akinobu Mita
2011-04-24 9:51 ` Akinobu Mita
2011-04-25 21:33 ` Andrew Morton
2011-04-26 2:00 ` Akinobu Mita
2011-04-24 9:51 ` [PATCH 6/6] m68knommu: fix build error due to the lack of find_next_bit_le() Akinobu Mita
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=1303820600.3125.13.camel@hcegtvedt \
--to=hans-christian.egtvedt@atmel.com \
--cc=akinobu.mita@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=geert@linux-m68k.org \
--cc=gerg@uclinux.org \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux390@de.ibm.com \
--cc=linux@arm.linux.org.uk \
--cc=schwidefsky@de.ibm.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).