From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Bastian Blank <bastian@waldi.eu.org>,
linuxppc-dev@ozlabs.org, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix ext4 bitops
Date: Mon, 4 Feb 2008 10:52:59 +0530 [thread overview]
Message-ID: <20080204052259.GB7494@skywalker> (raw)
In-Reply-To: <20080201200240.GA28566@wavehammer.waldi.eu.org>
On Fri, Feb 01, 2008 at 09:02:40PM +0100, Bastian Blank wrote:
> Fix ext4 bitops.
>
> Signed-off-by: Bastian Blank <waldi@debian.org>
>
> diff --git a/include/asm-powerpc/bitops.h b/include/asm-powerpc/bitops.h
> index 220d9a7..d0980df 100644
> --- a/include/asm-powerpc/bitops.h
> +++ b/include/asm-powerpc/bitops.h
> @@ -363,6 +363,8 @@ unsigned long generic_find_next_le_bit(const unsigned long *addr,
> unsigned long size, unsigned long offset);
> /* Bitmap functions for the ext2 filesystem */
>
> +#include <asm-generic/bitops/le.h>
> +
> #define ext2_set_bit(nr,addr) \
> __test_and_set_le_bit((nr), (unsigned long*)addr)
> #define ext2_clear_bit(nr, addr) \
I am not sure what the changes are for. Can you send me the build logs
with the compile error. I always test Ext4 on powerpc so not sure what
went wrong.
-aneesh
next prev parent reply other threads:[~2008-02-04 5:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-01 20:02 [PATCH] Fix ext4 bitops Bastian Blank
2008-02-03 7:36 ` Benjamin Herrenschmidt
2008-02-04 5:22 ` Aneesh Kumar K.V [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-02-01 20:02 Bastian Blank
2008-02-01 20:22 ` Andrew Morton
2008-02-01 21:04 ` Bastian Blank
2008-02-03 12:12 ` Heiko Carstens
2008-02-03 12:39 ` Geert Uytterhoeven
2008-02-03 12:39 ` Geert Uytterhoeven
2008-02-04 4:50 ` Aneesh Kumar K.V
2008-02-04 4:50 ` Aneesh Kumar K.V
2008-02-04 9:24 ` Heiko Carstens
2008-02-04 9:24 ` Heiko Carstens
2008-02-04 9:29 ` Aneesh Kumar K.V
2008-02-04 9:29 ` Aneesh Kumar K.V
2008-02-04 20:11 ` Geert Uytterhoeven
2008-02-04 20:11 ` Geert Uytterhoeven
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=20080204052259.GB7494@skywalker \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=bastian@waldi.eu.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.