From: Mingming Cao <cmm@us.ibm.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
linux-arch@vger.kernel.org
Subject: Re: ext4 still broken on arm (at least)
Date: Wed, 28 Nov 2007 08:45:59 -0800 [thread overview]
Message-ID: <474D9B47.80209@us.ibm.com> (raw)
In-Reply-To: <20071127214308.5215a6a2.akpm@linux-foundation.org>
Andrew Morton wrote:
> On Wed, 28 Nov 2007 11:00:20 +0530 "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com> wrote:
>
>> On Tue, Nov 27, 2007 at 09:14:44PM -0800, Andrew Morton wrote:
>>> fs/ext4/mballoc.c: In function `ext4_mb_generate_buddy':
>>> fs/ext4/mballoc.c:836: error: implicit declaration of function `ext2_find_next_bit'
>>
>> I actually sent in a patch which changes asking for review to
>> linux-arch. I haven't got the response yet.
>
> Don't expect one...
>
>> Attaching the patch
>> below
>
>
>> Introduce ext4_find_next_bit
>>
>> From: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
>>
>> This gets used by the ext4 multi block allocator patches.
>>
>> Also add generic_find_next_le_bit
>>
>> Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
>> Cc: <linux-ext4@vger.kernel.org>
>> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
>> ---
>>
>> include/asm-arm/bitops.h | 2 +
>> include/asm-generic/bitops/ext2-non-atomic.h | 2 +
>> include/asm-generic/bitops/le.h | 4 ++
>> include/asm-m68k/bitops.h | 2 +
>> include/asm-m68knommu/bitops.h | 2 +
>> include/asm-powerpc/bitops.h | 4 ++
>> include/asm-s390/bitops.h | 2 +
>> include/linux/ext4_fs.h | 1 +
>> lib/find_next_bit.c | 43 ++++++++++++++++++++++++++
>
> May as well merge it I guess. I'll do that. Possibly it should be
> merged into the ext4 tree instead, so that people can build the ext4 devel
> tree on other architectures but obviously there's no call for that.
>
I will merge it to ext4 development tree.
Mingming
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2007-11-28 16:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-28 5:14 ext4 still broken on arm (at least) Andrew Morton
2007-11-28 5:30 ` Aneesh Kumar K.V
2007-11-28 5:43 ` Andrew Morton
2007-11-28 8:28 ` Russell King
2007-11-28 16:45 ` Mingming Cao [this message]
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=474D9B47.80209@us.ibm.com \
--to=cmm@us.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-ext4@vger.kernel.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.