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 X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 52905C5DF61 for ; Thu, 7 Nov 2019 08:35:41 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 0C0AF21D79 for ; Thu, 7 Nov 2019 08:35:41 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=linaro.org header.i=@linaro.org header.b="VL6srznp" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726991AbfKGIfk (ORCPT ); Thu, 7 Nov 2019 03:35:40 -0500 Received: from mail-lj1-f193.google.com ([209.85.208.193]:45558 "EHLO mail-lj1-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726734AbfKGIfk (ORCPT ); Thu, 7 Nov 2019 03:35:40 -0500 Received: by mail-lj1-f193.google.com with SMTP id n21so1242926ljg.12 for ; Thu, 07 Nov 2019 00:35:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=XWbS4SdBYwL/ccROShNKX81fMjG6lxwrEjt2noFM/g4=; b=VL6srznpuYCV6D/0lZVlzDN+dlBUW4KvdMm/FC0QPAchGwVCGmPRjDRkZOrwPG+bUb mNYDV75Rh9xdzW2sxvyv3ZLhGTEliWMqctGp3AcrRZso3pAuFdFIZaQ8EAjHPdDBttto d5xpGBhs9szzSBHAxyLA1Ijgkm/emiQCBJprzDHKVgPRZ6UHUOugftCl7bhusCW5Sw+O anCvH2HLSKaTShd2wpaPlo3ztvLzJxsEW2rDXvluQx8Kzym4Slex22gz04piaWkfObU5 paEuwRx3DOdxXNsfLj1qWXuKfJFLfh11I1KqhIh9IZCs3Yxq7rbejByObTbbHOs5Z9sT g6cg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=XWbS4SdBYwL/ccROShNKX81fMjG6lxwrEjt2noFM/g4=; b=UEHbpNORHXTHwQ/qMz9Q5siAwlpIZkshXUeP0zZP++hgThU31S+4I2GRXCPJuZHZ6Y wBetDz59I3tF+DKmUFMYhXtDZWwRiCwLkLH4VQL95tPUdGzhwLF+beY/fm8DJSQo09DZ f/2AJQcC35M68qg5BnA6PX+XEBBHY9Qjc1ROmcdD2GykRbD7diG8dIU6sOtdzybzjY1x zLieMpyNPeZPkNxUiSZa4er+jsOwD8D7z8CP0BpnQz26psfdjmLcc2lB++majPx73ynM FOcL8BaWfsrNnExpzdkuINlsvUevJhcx/yC5v+0nHYljf7iuEShGpe+GQy+rP1Z7bQD9 kMcg== X-Gm-Message-State: APjAAAX2drlUESf6STV5QbYdsRzZF7/0jhNRtf3jyt0VdsPzprRvtDUA NwBicEXoqBlkeBUvs3jmiEKvG6JI68Cqti6psAT6jw== X-Google-Smtp-Source: APXvYqzLDy5kAcOhUPus7hOmfrlIFJdTpXZx1CGpWRbjO0h59ftvmHkp6F8fGRO+IoMHNXYUgHfXo8+pTOKnk5Y6Zyk= X-Received: by 2002:a2e:9a12:: with SMTP id o18mr1400915lji.191.1573115738391; Thu, 07 Nov 2019 00:35:38 -0800 (PST) MIME-Version: 1.0 References: <20191105174359.01cb034f@canb.auug.org.au> In-Reply-To: <20191105174359.01cb034f@canb.auug.org.au> From: Linus Walleij Date: Thu, 7 Nov 2019 09:35:27 +0100 Message-ID: Subject: Re: linux-next: build warning after merge of the gpio tree To: Stephen Rothwell Cc: Linux Next Mailing List , Linux Kernel Mailing List , Chris Packham Content-Type: text/plain; charset="UTF-8" Sender: linux-next-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-next@vger.kernel.org On Tue, Nov 5, 2019 at 7:44 AM Stephen Rothwell wrote: > After merging the gpio tree, today's linux-next build (arm > multi_v7_defconfig) produced this warning: > > WARNING: vmlinux.o(.data+0xbd3f4): Section mismatch in reference from the variable bcm_iproc_gpio_driver to the (unknown reference) .init.rodata:(unknown) > The variable bcm_iproc_gpio_driver references > the (unknown reference) __initconst (unknown) > If the reference is valid then annotate the > variable with __init* or __refdata (see linux/init.h) or name the variable: > *_template, *_timer, *_sht, *_ops, *_probe, *_probe_one, *_console > > (and similar for x86_64 allmodconfig) > > Introduced by commit > > 6a41b6c5fc20 ("gpio: Add xgs-iproc driver") Mark Brown finally hunted this down and fixed. It should be fine in my for-next branch now. Yours, Linus Walleij