[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <56214FC3.2060002@gmail.com>
Date: Fri, 16 Oct 2015 12:28:03 -0700
From: Florian Fainelli <f.fainelli@...il.com>
To: Arnd Bergmann <arnd@...db.de>, linux-arm-kernel@...ts.infradead.org
CC: Brian Norris <computersforpeace@...il.com>,
Mark Rutland <mark.rutland@....com>,
devicetree@...r.kernel.org,
Florian Fainelli <f.fainelli@...il.com>,
Pawel Moll <pawel.moll@....com>,
Anup Patel <anup.patel@...adcom.com>,
Scott Branden <sbranden@...adcom.com>,
Ian Campbell <ijc+devicetree@...lion.org.uk>,
Catalin Marinas <catalin.marinas@....com>,
Kumar Gala <galak@...eaurora.org>,
Will Deacon <will.deacon@....com>,
linux-kernel@...r.kernel.org,
Vikram Prakash <vikramp@...adcom.com>,
Rob Herring <robh+dt@...nel.org>,
linux-mtd@...ts.infradead.org,
Sandeep Tripathy <tripathy@...adcom.com>,
Ray Jui <rjui@...adcom.com>,
Pramod KUMAR <pramodku@...adcom.com>,
bcm-kernel-feedback-list@...adcom.com,
David Woodhouse <dwmw2@...radead.org>
Subject: Re: [PATCH v2 2/4] mtd: nand: Allow MTD_NAND_BRCMNAND to be selected
for ARM64
On 16/10/15 12:25, Arnd Bergmann wrote:
> On Friday 16 October 2015 09:54:45 Brian Norris wrote:
>>> MTD_NAND_BRCMNAND uses the generic nand functions, but is currently allowed
>>> to be built without CONFIG_MTD_NAND, which results in a link error:
>>>
>>> drivers/built-in.o: In function `brcmnand_remove':
>>> coresight-replicator.c:(.text+0x17ae6c): undefined reference to `nand_release'
>>> drivers/built-in.o: In function `brcmnand_probe':
>>> coresight-replicator.c:(.text+0x17d4b4): undefined reference to `nand_scan_ident'
>>> coresight-replicator.c:(.text+0x17d948): undefined reference to `nand_scan_tail'
>>
>> How did you get this? MTD_NAND_BRCMNAND is surrounded in the
>> 'if MTD_NAND' block, which implicitly generates a MTD_NAND dependency.
>> And I can confirm that in menuconfig, I see this when I disable MTD_NAND
>> and search for BRCMNAND:
>>
>> Symbol: MTD_NAND_BRCMNAND [=n]
>> Type : tristate
>> Prompt: Broadcom STB NAND controller
>> Location:
>> -> Device Drivers
>> -> Memory Technology Device (MTD) support (MTD [=y])
>> (1) -> NAND Device Support (MTD_NAND [=n])
>> Defined at drivers/mtd/nand/Kconfig:394
>> Depends on: MTD [=y] && MTD_NAND [=n] && (ARM [=y] || ARM64 || MIPS)
>
> Sorry, can't reproduce it any more. My patch is dated June 4, so it was
> probably broken then but got fixed since. I normally try to verify that
> the patches are still needed before I send them, but this time I only
> saw the current discussion and remembered something vague about it
> and sent what I had in my backlog of the randconfig-fixes series.
It may have been a problem before this patch:
d80d942bcc8e1555a76774d20be9800cfef2d415 ("ARM: BCM: Do not select
CONFIG_MTD_NAND_BRCMNAND")
--
Florian
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists