Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752183Ab2FTEY2 (ORCPT ); Wed, 20 Jun 2012 00:24:28 -0400 Received: from shards.monkeyblade.net ([149.20.54.216]:33538 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751061Ab2FTEY0 (ORCPT ); Wed, 20 Jun 2012 00:24:26 -0400 Date: Tue, 19 Jun 2012 21:24:23 -0700 (PDT) Message-Id: <20120619.212423.1927278993583357087.davem@davemloft.net> To: sfr@canb.auug.org.au Cc: netdev@vger.kernel.org, linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, federico.vaga@gmail.com, giancarlo.asnaghi@st.com, wg@grandegger.com, bhupesh.sharma@st.com, mkl@pengutronix.de Subject: Re: linux-next: build failure after merge of the net-next tree From: David Miller In-Reply-To: <20120620133348.a9ff31a72ffd11818f574fe3@canb.auug.org.au> References: <20120620133348.a9ff31a72ffd11818f574fe3@canb.auug.org.au> X-Mailer: Mew version 6.5 on Emacs 24.0.97 / Mule 6.0 (HANACHIRUSATO) 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 Content-Length: 913 Lines: 23 From: Stephen Rothwell Date: Wed, 20 Jun 2012 13:33:48 +1000 > After merging the net-next tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > ERROR: "clk_get_rate" [drivers/net/can/c_can/c_can_pci.ko] undefined! > ERROR: "clk_get" [drivers/net/can/c_can/c_can_pci.ko] undefined! > ERROR: "clk_put" [drivers/net/can/c_can/c_can_pci.ko] undefined! > > Caused by commit 5b92da0443c2 ("c_can_pci: generic module for C_CAN/D_CAN > on PCI"). Maybe a missing Kconfig dependency/select? > > I have used the net-next tree from next-20120619 for today. Known problem: http://marc.info/?l=linux-netdev&m=134014347620836&w=2 -- 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/