From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752484AbdBIBS1 (ORCPT ); Wed, 8 Feb 2017 20:18:27 -0500 Received: from ozlabs.org ([103.22.144.67]:46787 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751636AbdBIBS0 (ORCPT ); Wed, 8 Feb 2017 20:18:26 -0500 Date: Thu, 9 Feb 2017 12:08:39 +1100 From: Stephen Rothwell To: Brian Norris Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Linus Walleij Subject: linux-next: build failure after merge of the l2-mtd tree Message-ID: <20170209120839.50a8cfdb@canb.auug.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Brian, After merging the l2-mtd tree, today's linux-next build (x86_64 allmodconfig) failed like this: ERROR: "of_flash_probe_versatile" [drivers/mtd/maps/physmap_of.ko] undefined! ERROR: "of_flash_probe_gemini" [drivers/mtd/maps/physmap_of.ko] undefined! Probably caused by commit 56ff337ea433 ("mtd: physmap_of: add a hook for Gemini flash probing") The config has: CONFIG_MTD_PHYSMAP=m CONFIG_MTD_PHYSMAP_COMPAT=y CONFIG_MTD_PHYSMAP_OF=m CONFIG_MTD_PHYSMAP_OF_VERSATILE=y CONFIG_MTD_PHYSMAP_OF_GEMINI=y I am not sure why this is a problem, but previously physmap_of_versatile.o would have been in obj-m and it is now in obj-y. I have used the version fo the l2-mtd tree from next-20170208 for today. -- Cheers, Stephen Rothwell