[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160201121834.GJ17997@ZenIV.linux.org.uk>
Date: Mon, 1 Feb 2016 12:18:34 +0000
From: Al Viro <viro@...IV.linux.org.uk>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: Linux-Arch <linux-arch@...r.kernel.org>,
linux-kbuild <linux-kbuild@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 05/12] m68k: move exports to definitions
On Mon, Feb 01, 2016 at 11:52:27AM +0100, Geert Uytterhoeven wrote:
> Hi Al,
>
> On Fri, Jan 29, 2016 at 8:18 PM, Al Viro <viro@...iv.linux.org.uk> wrote:
> > From: Al Viro <viro@...iv.linux.org.uk>
> >
> > the rest of architectures should just use generic-y += export.h in
> > asm/Kbuild
> >
> > Signed-off-by: Al Viro <viro@...iv.linux.org.uk>
>
> Looks good, and (some of, not all) the symbols end up in kstrtab, so
>
> Acked-by: Geert Uytterhoeven <geert@...ux-m68k.org>
>
> Note that none of the m68k defconfigs build modules that refer to these
> symbols. This changes completely with allmodconfig, which adds lots of
> references in many of the same modules.
> CONFIG_LBDAF=y is set in the defconfigs.
>
> Unfortunately I haven't managed to boot a kernel that uses these symbols
> in modules...
Details, please... Which symbols are missing?
Powered by blists - more mailing lists