From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (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 CDAF32F0688; Thu, 4 Sep 2025 09:23:23 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1756977803; cv=none; b=dICGMq5mQlUyvF1iVSfwsOsAumm6YRada+4WuVdcRwtzAgFbUbP7LkAqQ8lk4yG4sLf6qyNCD/E0VbV4af7oqc3ZWYCh88yJEWDqiBlwjeJbQGYN85tgDF9F/dHlE5ZSkbarvSUGaTP4DEWIUDPDR6rE+qSdnC+IlM97QD859E0= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1756977803; c=relaxed/simple; bh=8qUNR5uk4ZoW60qCbqxX2WVE+fxq/h7F4lEPZWAqJVo=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=VUv/T5EhSyfMIsW9/vmPZQm641tS4Fa0MrSTQy9TjKlC8bICjefXWeqMTFc9F3Nj1td5eS4deKEsxNHhGesSWQDoXqSX6ks7mRCHhRCBnOA/6l8YdmeVmCi85PTsqykQie1+jV7yjCUZff02Cg7HWfqoMqFk5tdY9piq93mXY/I= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=sSx/Tbs3; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="sSx/Tbs3" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 2B1C7C4CEF1; Thu, 4 Sep 2025 09:23:22 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1756977803; bh=8qUNR5uk4ZoW60qCbqxX2WVE+fxq/h7F4lEPZWAqJVo=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=sSx/Tbs3Mrrspkf4MULYwZBqL4rlQa7J+UoDxCdv5YfA7muXFwkJcLCOQKFiy3KmT N/BA079OMVlUgWSrSd2xF5p2+G9WS4tD/irCSCkTKj3OUtpgsF2L06yLsNWDSkLRCu 8ApaRmWydy5hq0r07WfQZV6GOkv3/Mhs7nROD5ZLRfslCE7loqgBV6fWXOSzVl1KMn +RdBgZvIlwXttmohkWbTRFxUo20IJ7QOWfGy7gLCW2/J2eaRRiPqY3ZjuCZMSYfO0u xBdGWzbS+CFZE64zd/2Ww8cMSrbjKthJVxiBAYzvqY3xyutVYhJU/OJjAreOjEyZwQ Sm202kIvoMcHA== Date: Thu, 4 Sep 2025 10:23:19 +0100 From: Lee Jones To: Bartosz Golaszewski Cc: Stephen Rothwell , Alexander Stein , Linux Kernel Mailing List , Linux Next Mailing List Subject: Re: linux-next: build failure after merge of the mfd tree Message-ID: <20250904092319.GG2764654@google.com> References: <20250904154122.63acc45c@canb.auug.org.au> <20250904063043.GE2764654@google.com> Precedence: bulk X-Mailing-List: linux-next@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: On Thu, 04 Sep 2025, Bartosz Golaszewski wrote: > On Thu, 4 Sept 2025 at 08:30, Lee Jones wrote: > > > > On Thu, 04 Sep 2025, Stephen Rothwell wrote: > > > > > Hi all, > > > > > > After merging the mfd tree, today's linux-next build (x86_64 allmodconfig) > > > failed like this: > > > > > > x86_64-linux-gnu-ld: vmlinux.o: in function `stmpe_gpio_get': > > > gpio-stmpe.c:(.text+0x21a7c29): undefined reference to `stmpe_reg_read' > > > x86_64-linux-gnu-ld: vmlinux.o: in function `stmpe_gpio_get_direction': > > > gpio-stmpe.c:(.text+0x21a7db2): undefined reference to `stmpe_reg_read' > > > x86_64-linux-gnu-ld: vmlinux.o: in function `stmpe_gpio_irq_sync_unlock': > > > gpio-stmpe.c:(.text+0x21a8166): undefined reference to `stmpe_reg_write' > > > x86_64-linux-gnu-ld: gpio-stmpe.c:(.text+0x21a82ef): undefined reference to `stmpe_reg_read' > > > x86_64-linux-gnu-ld: gpio-stmpe.c:(.text+0x21a8372): undefined reference to `stmpe_reg_read' > > > x86_64-linux-gnu-ld: vmlinux.o: in function `stmpe_gpio_irq': > > > gpio-stmpe.c:(.text+0x21a8c27): undefined reference to `stmpe_block_read' > > > x86_64-linux-gnu-ld: gpio-stmpe.c:(.text+0x21a8f05): undefined reference to `stmpe_reg_write' > > > x86_64-linux-gnu-ld: gpio-stmpe.c:(.text+0x21a8f89): undefined reference to `stmpe_reg_write' > > > x86_64-linux-gnu-ld: vmlinux.o: in function `stmpe_gpio_disable': > > > gpio-stmpe.c:(.text+0x21a91dc): undefined reference to `stmpe_disable' > > > x86_64-linux-gnu-ld: vmlinux.o: in function `stmpe_gpio_set': > > > gpio-stmpe.c:(.text+0x21a93a4): undefined reference to `stmpe_reg_write' > > > x86_64-linux-gnu-ld: gpio-stmpe.c:(.text+0x21a941e): undefined reference to `stmpe_set_bits' > > > x86_64-linux-gnu-ld: vmlinux.o: in function `stmpe_gpio_direction_output': > > > gpio-stmpe.c:(.text+0x21a95a4): undefined reference to `stmpe_set_bits' > > > x86_64-linux-gnu-ld: vmlinux.o: in function `stmpe_gpio_direction_input': > > > gpio-stmpe.c:(.text+0x21a9705): undefined reference to `stmpe_set_bits' > > > x86_64-linux-gnu-ld: vmlinux.o: in function `stmpe_gpio_request': > > > gpio-stmpe.c:(.text+0x21a983e): undefined reference to `stmpe_set_altfunc' > > > x86_64-linux-gnu-ld: vmlinux.o: in function `stmpe_dbg_show_one': > > > gpio-stmpe.c:(.text+0x21a99c0): undefined reference to `stmpe_reg_read' > > > x86_64-linux-gnu-ld: gpio-stmpe.c:(.text+0x21a9b8c): undefined reference to `stmpe_reg_read' > > > x86_64-linux-gnu-ld: gpio-stmpe.c:(.text+0x21a9bb1): undefined reference to `stmpe_reg_read' > > > x86_64-linux-gnu-ld: gpio-stmpe.c:(.text+0x21a9c61): undefined reference to `stmpe_reg_read' > > > x86_64-linux-gnu-ld: gpio-stmpe.c:(.text+0x21a9e6c): undefined reference to `stmpe_reg_read' > > > x86_64-linux-gnu-ld: vmlinux.o: in function `stmpe_gpio_probe': > > > gpio-stmpe.c:(.text+0x21aa5b2): undefined reference to `stmpe_enable' > > > x86_64-linux-gnu-ld: gpio-stmpe.c:(.text+0x21aa83e): undefined reference to `stmpe_disable' > > > > > > Presumably caused by commit > > > > > > e160dd0ac8c3 ("mfd: stmpe: Allow building as module") > > > > Okay, I have removed this patch until it can be better tested. > > > > > I have used the mfd tree from next-20250903 for today. > > > > > > Note that commit > > > > > > 03db20aaa3ba ("gpio: stmpe: Allow to compile as a module") > > > > > > is in the gpio-brgl tree which has not been merged into linux-next at > > > this point. > > > > Okay, perhaps these need to go in together then. > > > > Thanks Stephen. > > > > I can take it through the GPIO tree if you will and set up an > immutable branch for you. Or not if the potential conflict is minimal. An IB would be good. Thank you. -- Lee Jones [李琼斯]