From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail.ozlabs.org (gandalf.ozlabs.org [150.107.74.76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 4B8901877; Thu, 16 May 2024 02:42:07 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=150.107.74.76 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1715827333; cv=none; b=JGRLwqVLTHVawKCCfCRBpvZHUWGmcW3T6EEvJc0U4HEIuW27Zls6RSJbUX5fnLWJ9p7W5lzbw8pdvCxRfJUGDRCf9kch940kGA3EMVwVYqXNjRdQtrg+rJovdpKKWtB4TEO/ugJjiH/j/UHYyJnTTDUXMaG6ImN9Wej50KgWsSU= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1715827333; c=relaxed/simple; bh=iVSKuxqhWqP0pGI+v769ZkjrMQDRcsRIXy/mVC+Gwzo=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=WEJ9nbBuMG7GViuUOISkHbp9xdeixqNp3z7J40Nlo5Y+vuaNEpLbW/DKGgN72szGkN0eLqgZ5MuWuKPSleCQsl9/JHscEyz1K1QAlH3AyBpxRBTc3ybqHhk13TH9QVyrjUdHVdFNGE7x/7CiFSCGNyiO1WhiGkWNfvdttINUtTo= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=ellerman.id.au; spf=pass smtp.mailfrom=ellerman.id.au; dkim=pass (2048-bit key) header.d=ellerman.id.au header.i=@ellerman.id.au header.b=IoYrDqUy; arc=none smtp.client-ip=150.107.74.76 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=ellerman.id.au Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=ellerman.id.au Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=ellerman.id.au header.i=@ellerman.id.au header.b="IoYrDqUy" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ellerman.id.au; s=201909; t=1715827326; bh=iVSKuxqhWqP0pGI+v769ZkjrMQDRcsRIXy/mVC+Gwzo=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=IoYrDqUyv9fqD7HsO/MKcHPWSmQsZJQtViDC5HpvjTv20kA5uhx4yRBYvSXIVRTrz WgeNhlK5sXMYfIaZowrZ/OuXLBAZjfLO1synJV+yIMeUOMgVVULLmUgQxe8WfAa6Cp so0+e/9TsQ9BN46+PqDNTHXlqryEdtrmdRDoI/j4ytqFAtRfoSWa7VUQGRbohz8szo wxC6Be38msSgwRqgYvNgxyIv5aJz2dFpmSi+857dD8QsWtf2xgZT9iINtKxNqH7tF1 J8vDeAt1rU3+ZBoC/LDlVlxEMMJK4+IyXLde+um/HSsHZ9muBnLPVpRHVO+Hnx2OgC rmLT/kRUvwJkQ== Received: from authenticated.ozlabs.org (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail.ozlabs.org (Postfix) with ESMTPSA id 4VfvWK6ZJhz4wcR; Thu, 16 May 2024 12:42:05 +1000 (AEST) From: Michael Ellerman To: Stephen Rothwell , PowerPC Cc: Hari Bathini , Linux Kernel Mailing List , Linux Next Mailing List Subject: Re: linux-next: build warning after merge of the powerpc tree In-Reply-To: <20240515163708.3380c4d1@canb.auug.org.au> References: <20240515163708.3380c4d1@canb.auug.org.au> Date: Thu, 16 May 2024 12:42:01 +1000 Message-ID: <87cypmwk92.fsf@mail.lhotse> Precedence: bulk X-Mailing-List: linux-next@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain Stephen Rothwell writes: > Hi all, > > After merging the powerpc tree, today's (it may have been yesterday's) > linux-next build (powerpc allyesconfig) produced this warning: > > WARNING: modpost: vmlinux: section mismatch in reference: fadump_setup_param_area+0x200 (section: .text.fadump_setup_param_area) -> memblock_phys_alloc_range (section: .init.text) I don't see the warning, but clearly it is possible if the compiler decides not to inline fadump_setup_param_area(). What compiler version are you using? cheers From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from lists.ozlabs.org (lists.ozlabs.org [112.213.38.117]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 4D212C25B75 for ; Thu, 16 May 2024 02:42:53 +0000 (UTC) Authentication-Results: lists.ozlabs.org; dkim=fail reason="signature verification failed" (2048-bit key; unprotected) header.d=ellerman.id.au header.i=@ellerman.id.au header.a=rsa-sha256 header.s=201909 header.b=IoYrDqUy; dkim-atps=neutral Received: from boromir.ozlabs.org (localhost [IPv6:::1]) by lists.ozlabs.org (Postfix) with ESMTP id 4VfvXC1Kwcz3dKS for ; Thu, 16 May 2024 12:42:51 +1000 (AEST) Authentication-Results: lists.ozlabs.org; dmarc=none (p=none dis=none) header.from=ellerman.id.au Authentication-Results: lists.ozlabs.org; dkim=pass (2048-bit key; unprotected) header.d=ellerman.id.au header.i=@ellerman.id.au header.a=rsa-sha256 header.s=201909 header.b=IoYrDqUy; dkim-atps=neutral Received: from mail.ozlabs.org (mail.ozlabs.org [IPv6:2404:9400:2221:ea00::3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 4VfvWL0qLKz30V1 for ; Thu, 16 May 2024 12:42:06 +1000 (AEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ellerman.id.au; s=201909; t=1715827326; bh=iVSKuxqhWqP0pGI+v769ZkjrMQDRcsRIXy/mVC+Gwzo=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=IoYrDqUyv9fqD7HsO/MKcHPWSmQsZJQtViDC5HpvjTv20kA5uhx4yRBYvSXIVRTrz WgeNhlK5sXMYfIaZowrZ/OuXLBAZjfLO1synJV+yIMeUOMgVVULLmUgQxe8WfAa6Cp so0+e/9TsQ9BN46+PqDNTHXlqryEdtrmdRDoI/j4ytqFAtRfoSWa7VUQGRbohz8szo wxC6Be38msSgwRqgYvNgxyIv5aJz2dFpmSi+857dD8QsWtf2xgZT9iINtKxNqH7tF1 J8vDeAt1rU3+ZBoC/LDlVlxEMMJK4+IyXLde+um/HSsHZ9muBnLPVpRHVO+Hnx2OgC rmLT/kRUvwJkQ== Received: from authenticated.ozlabs.org (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail.ozlabs.org (Postfix) with ESMTPSA id 4VfvWK6ZJhz4wcR; Thu, 16 May 2024 12:42:05 +1000 (AEST) From: Michael Ellerman To: Stephen Rothwell , PowerPC Subject: Re: linux-next: build warning after merge of the powerpc tree In-Reply-To: <20240515163708.3380c4d1@canb.auug.org.au> References: <20240515163708.3380c4d1@canb.auug.org.au> Date: Thu, 16 May 2024 12:42:01 +1000 Message-ID: <87cypmwk92.fsf@mail.lhotse> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: linuxppc-dev@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Linux Next Mailing List , Linux Kernel Mailing List , Hari Bathini Errors-To: linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Sender: "Linuxppc-dev" Stephen Rothwell writes: > Hi all, > > After merging the powerpc tree, today's (it may have been yesterday's) > linux-next build (powerpc allyesconfig) produced this warning: > > WARNING: modpost: vmlinux: section mismatch in reference: fadump_setup_param_area+0x200 (section: .text.fadump_setup_param_area) -> memblock_phys_alloc_range (section: .init.text) I don't see the warning, but clearly it is possible if the compiler decides not to inline fadump_setup_param_area(). What compiler version are you using? cheers