DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=googlemail.com; s=gamma;
        h=mime-version:reply-to:date:message-id:subject:from:to:cc
         :content-type;
        b=by8vZG/ayZXdWxr5vjCoT2vIKqJa2x/spBuOX8OjhjG865BUpaImCJZVIjJwsyxZU7
         38vTEfFWTBO0hOn/Mc+4sqddkqe/+oqcQLmnmF2YPQKXnXj3mzK/R5FXFLb6SINGzE7M
         WT19IBn/zjCnAeaO98mNbbFjMkHahTIEQZJZU=
MIME-Version: 1.0
Reply-To: sedat.dilek@gmail.com
Date: Fri, 1 Apr 2011 17:55:52 +0200
Message-ID: <AANLkTi=td3J2duwv9RuXJHquA6=wRRq8vWLkJY97xtP9@mail.gmail.com>
Subject: Re: linux-next: Tree for April 1 [BROKEN ubifs when CONFIG_DEBUG_SECTION_MISMATCH=y]
From: Sedat Dilek <sedat.dilek@googlemail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Content-Type: text/plain; charset=UTF-8
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 995
Lines: 33

On Fri, Apr 1, 2011 at 5:25 AM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi all,
>
> Changes since 20110331:
>
> Dropped tree: xen
>
> The sparc-current tree lost its build failure.
>
> The gfs2 tree gained a conflict against Linus' tree.
>
> The tip tree gained a build failure (due to a change in the bjdooks-i2c
> tree) for which I applied a patch.
>

With CONFIG_DEBUG_SECTION_MISMATCH=y set, I see in my build.log:
...
MODPOST 2742 modules
...
ERROR: "empty_aops" [fs/ubifs/ubifs.ko] undefined!
make[5]: *** [__modpost] Error 1
make[4]: *** [modules] Error 2
make[3]: *** [sub-make] Error 2
make[2]: *** [all] Error 2
make[2]: Leaving directory
`/home/sd/src/linux-2.6/linux-2.6.39-rc1/debian/build/build_i386_none_686-iniza'

- Sedat -
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/