From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755275Ab3KEORR (ORCPT ); Tue, 5 Nov 2013 09:17:17 -0500 Received: from mga02.intel.com ([134.134.136.20]:51670 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754932Ab3KEORP (ORCPT ); Tue, 5 Nov 2013 09:17:15 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.93,640,1378882800"; d="scan'208";a="422580083" Date: Tue, 5 Nov 2013 06:17:02 -0800 From: Andi Kleen To: Rusty Russell Cc: Stephen Rothwell , linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org Subject: Re: linux-next: build warnings after merge of the modules tree Message-ID: <20131105141702.GE1962@tassilo.jf.intel.com> References: <20131104134134.48665968dd006e3310333993@canb.auug.org.au> <87fvrba8su.fsf@rustcorp.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87fvrba8su.fsf@rustcorp.com.au> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > modpost creates an entry when it sees the CRC, then when it sees the > actual symbol, it complains that it's seen it before. The preloaded > flag already exists for the equivalent case where we loaded from > Module.symvers, so use that. Looks good. Thanks for fixing. -Andi