From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932757Ab0BYOfH (ORCPT ); Thu, 25 Feb 2010 09:35:07 -0500 Received: from mail-qy0-f172.google.com ([209.85.221.172]:39167 "EHLO mail-qy0-f172.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932746Ab0BYOfE (ORCPT ); Thu, 25 Feb 2010 09:35:04 -0500 X-Greylist: delayed 347 seconds by postgrey-1.27 at vger.kernel.org; Thu, 25 Feb 2010 09:35:04 EST DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=GvWJNxkU8L7UT1rTnkypw00VC6h0qfTctUm12iIrV7fYYlFmkvynBUeYU90PLdJHyl F8c4z8bDDj3wm042v6ejZpI6zXb8f5Vkv3az9peyXG2RXNqetOXnKhC+dQD5Konjy8kj bBTMFCvRPvSVu33VUuxI9mruVxCGpGSF4vrE4= MIME-Version: 1.0 In-Reply-To: <10f740e81002250050g287f7753g96063376ecee9487@mail.gmail.com> References: <1266934273-9371-1-git-send-email-akinobu.mita@gmail.com> <20100224162152.GK3687@quack.suse.cz> <961aa3351002241738r7bbdc811p1fe80aabc336ae85@mail.gmail.com> <10f740e81002250050g287f7753g96063376ecee9487@mail.gmail.com> Date: Thu, 25 Feb 2010 23:29:14 +0900 Message-ID: <961aa3351002250629p11fc4a49m60aadbf79fc10696@mail.gmail.com> Subject: Re: [PATCH] udf: use ext2_find_next_bit From: Akinobu Mita To: Geert Uytterhoeven Cc: Jan Kara , linux-kernel@vger.kernel.org, Linux-Next Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 2010/2/25 Geert Uytterhoeven : > On Thu, Feb 25, 2010 at 02:38, Akinobu Mita wrote: >> 2010/2/25 Jan Kara : >>> On Tue 23-02-10 23:11:13, Akinobu Mita wrote: >>>> Use ext2_find_next_bit (generic_find_next_le_bit) to find the set bit >>>> in little endian bitmap region. > > Is any of this in linux-next now? > > http://kisskb.ellerman.id.au/kisskb/buildresult/2208481/ > | fs/udf/balloc.c:274: error: implicit declaration of function > 'generic_find_next_le_bit' Yep, Jan's patch caused the build breakage. Because generic_find_next_le_bit() is not available for all archtectures. So we should use ext2_find_next_bit() here.