From: Andrew Morton <akpm@linux-foundation.org>
To: Akinobu Mita <akinobu.mita@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
arnd@arndb.de, Martin Schwidefsky <schwidefsky@de.ibm.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
linux390@de.ibm.com, linux-s390@vger.kernel.org
Subject: Re: [PATCH 5/6] s390: use asm-generic/bitops/le.h
Date: Mon, 25 Apr 2011 14:33:19 -0700 [thread overview]
Message-ID: <20110425143319.f4c6e036.akpm@linux-foundation.org> (raw)
In-Reply-To: <1303638677-11211-6-git-send-email-akinobu.mita@gmail.com>
On Sun, 24 Apr 2011 18:51:16 +0900
Akinobu Mita <akinobu.mita@gmail.com> wrote:
> The previous style change enables to use asm-generic/bitops/le.h
> on s390.
What kernel version is this patchset against?
> }
> #define find_next_bit_le find_next_bit_le
>
> +#include <asm-generic/bitops/le.h>
> +
> #include <asm-generic/bitops/ext2-atomic-test.h>
>
Mainline arch/s390/include/asm/bitops.h doesn't have this inclusion.
Please recheck, redo and resend.
next prev parent reply other threads:[~2011-04-25 21:34 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
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 [this message]
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=20110425143319.f4c6e036.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=akinobu.mita@gmail.com \
--cc=arnd@arndb.de \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux390@de.ibm.com \
--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).