From: Geert Uytterhoeven <geert@linux-m68k.org>
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,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>
Subject: Re: [PATCH v3 2/7] arch: add #define for each of optimized find bitops
Date: Wed, 27 Apr 2011 16:00:28 +0200 [thread overview]
Message-ID: <BANLkTi=t4jFh58TSkgCt0YsweoEoO8TXvA@mail.gmail.com> (raw)
In-Reply-To: <1303910411-15793-3-git-send-email-akinobu.mita@gmail.com>
On Wed, Apr 27, 2011 at 15:20, Akinobu Mita <akinobu.mita@gmail.com> 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>
> Acked-by: Hans-Christian Egtvedt <hans-christian.egtvedt@atmel.com>
> Acked-by: Russell King <rmk+kernel@arm.linux.org.uk>
> Acked-by: Greg Ungerer <gerg@uclinux.org>
> Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>
> Cc: Heiko Carstens <heiko.carstens@de.ibm.com>
> Cc: Geert Uytterhoeven <geert@linux-m68k.org>
Acked-by: Geert Uytterhoeven <geert@linux-m68k.org>
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2011-04-27 14:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-27 13:20 [PATCH v3 0/7] remove CONFIG_GENERIC_FIND_{NEXT_BIT,BIT_LE,LAST_BIT} Akinobu Mita
2011-04-27 13:20 ` [PATCH v3 1/7] m68knommu: fix build error due to the lack of find_next_bit_le() Akinobu Mita
2011-04-27 13:20 ` Akinobu Mita
2011-05-03 6:58 ` Greg Ungerer
2011-05-03 9:11 ` Akinobu Mita
2011-05-03 9:12 ` Geert Uytterhoeven
2011-04-27 13:20 ` [PATCH v3 2/7] arch: add #define for each of optimized find bitops Akinobu Mita
2011-04-27 13:20 ` Akinobu Mita
2011-04-27 14:00 ` Geert Uytterhoeven [this message]
2011-04-27 13:20 ` [PATCH v3 3/7] bitops: add #ifndef for each of " Akinobu Mita
2011-04-27 13:20 ` Akinobu Mita
2011-04-27 13:20 ` [PATCH v3 4/7] arch: remove CONFIG_GENERIC_FIND_{NEXT_BIT,BIT_LE,LAST_BIT} Akinobu Mita
2011-04-27 13:20 ` Akinobu Mita
2011-04-27 13:20 ` [PATCH v3 5/7] arm: use asm-generic/bitops/le.h Akinobu Mita
2011-04-27 13:20 ` [PATCH v3 6/7] s390: " Akinobu Mita
2011-04-27 13:20 ` Akinobu Mita
2011-04-27 13:20 ` [PATCH v3 7/7] m68knommu: use generic 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='BANLkTi=t4jFh58TSkgCt0YsweoEoO8TXvA@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=akinobu.mita@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).