From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1764680AbXGYHzd (ORCPT ); Wed, 25 Jul 2007 03:55:33 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1758218AbXGYHzX (ORCPT ); Wed, 25 Jul 2007 03:55:23 -0400 Received: from gate.crashing.org ([63.228.1.57]:54686 "EHLO gate.crashing.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751966AbXGYHzW (ORCPT ); Wed, 25 Jul 2007 03:55:22 -0400 Subject: Re: modpost warning question From: Benjamin Herrenschmidt To: Kumar Gala Cc: sam@ravnborg.org, linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org, Jeff Garzik , netdev@vger.kernel.org In-Reply-To: References: Content-Type: text/plain Date: Wed, 25 Jul 2007 17:55:03 +1000 Message-Id: <1185350103.5439.314.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.10.1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 2007-07-25 at 02:14 -0500, Kumar Gala wrote: > I'm seeing the following warning: > > WARNING: vmlinux.o(.init.text+0x1acdc): Section mismatch: reference to > .exit.text:gfar_mdio_exit (between 'gfar_init' and 'gfar_mdio_init') > > I don't understand why its not ok to access .exit.text from .init.text > > The following addresses the issue, however I don't particularly like it: Because exit.text is removed when compiling built-in Ben.