Received: by 2002:a05:6a10:f347:0:0:0:0 with SMTP id d7csp4350924pxu; Tue, 1 Dec 2020 02:46:08 -0800 (PST) X-Google-Smtp-Source: ABdhPJwB1q2mO5SirAy8x54ry84sIOZUqTNwYJieZGuhJYOpFrgNKvjMGW56Y5iGnFy60GhdIqiN X-Received: by 2002:a17:906:31d2:: with SMTP id f18mr2353013ejf.407.1606819567846; Tue, 01 Dec 2020 02:46:07 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1606819567; cv=none; d=google.com; s=arc-20160816; b=jWLdo4Hg2DB3HQZUnW0rkH9XzrnhKlBpfBBfUSy8M5zDksmBELrzfLSNAE6fY7YZvb EBJlSnCdbjJBaL2RbOMZyt4NuLqDda227wGMMD5eGHi2r88Vkgkl309JUKQamN8k9pVN par88W277XTEyMa3DdPl4BoYBEOhgaZJgmJYUwBdS9Q7/zph1VOYHx+KpOWggVYQQpQ9 gd+Ik+39JW2m+54ImYeqaxi/w++t1BkMYGsKm5nscxtV8bqKrEU9JyjFZN35cigi+tQX AgFSNAkVH5wuSrt0/9Ul64crtjFrp5YWGAqT3cv+7vPCXxTqmQ0qzmTvNk8dpRGlziih 5haw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=81YpZcAcK9Dri4QIgh3T/Rz81NMDik7HzMLHlDkb024=; b=e+mWt1U0nG+gXLvTJnFhtRBiT2stscCV+FgxAnsi9zFQBQ3S9VCD9KE2RRUiz/ww+I gZV8QiC9pTmQyrA2IJnOhZMZ/2e8OvBHfy00QNndY0n0t5guUdBF9c4rtnNXV8tFqMYQ OXgoQiaD5ZqZqRYyLLwZnEr6gYv2qcjW1cYF2GFV+Q5oqyIK9YHbJnvtdlDjBMllfVkS thvyK4RcSuCdKakQ3G6aWioZ5b779Sva/ALMOqR6eDKJkyg74FozmR0PaZXRKS0bJpwM LBFGYoD7oQ69Tx1TiiWrti2kYtoQsTGI40ftVDIfbsnGryynPiinnOkQ/FjJ90/xBOW4 qanA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=Gt1ozuGh; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id lx6si670497ejb.550.2020.12.01.02.45.45; Tue, 01 Dec 2020 02:46:07 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=Gt1ozuGh; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730164AbgLAKke (ORCPT + 99 others); Tue, 1 Dec 2020 05:40:34 -0500 Received: from mail.kernel.org ([198.145.29.99]:41206 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730152AbgLAKkd (ORCPT ); Tue, 1 Dec 2020 05:40:33 -0500 Received: from localhost (unknown [122.171.214.243]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 67E9520644; Tue, 1 Dec 2020 10:39:51 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1606819192; bh=t9r/K8kwhfWwjzpxV+Ixn5Vw8J6Duzp+cUWGXl1k5Bc=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=Gt1ozuGhI8oXKKmEPpk/w0W4Qhc2IHzBfhgX+M84OjnpA6ED8QOCc8gYJnNslB4gz fIxTj1IvxlWR7G/9Vo2voaY3auzSsDU13J9Iwx4ZcABJXVmn6CJPDAwCgKTO1jLeFS NH0Od1JBElYxi+ilqBbT3IUF4SRZfv4ONXsHsSBE= Date: Tue, 1 Dec 2020 16:09:47 +0530 From: Vinod Koul To: Sergio Paracuellos Cc: Stephen Rothwell , Kishon Vijay Abraham I , Linux Kernel Mailing List , Linux Next Mailing List Subject: Re: linux-next: build failure after merge of the phy-next tree Message-ID: <20201201103947.GZ8403@vkoul-mobl> References: <20201201170731.4c93b812@canb.auug.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 01-12-20, 07:45, Sergio Paracuellos wrote: > Hi Stephen, > > On Tue, Dec 1, 2020 at 7:07 AM Stephen Rothwell wrote: > > > > Hi all, > > > > After merging the phy-next tree, today's linux-next build (x86_64 > > allmodconfig) failed like this: > > > > drivers/phy/ralink/phy-mt7621-pci.c:17:10: fatal error: mt7621.h: No such file or directory > > 17 | #include > > | ^~~~~~~~~~ > > > > Caused by commit > > > > d87da32372a0 ("phy: ralink: Add PHY driver for MT7621 PCIe PHY") > > This driver has two includes which are in > "arch/mips/include/asm/mach-ralink" and are directly included in the > driver: > * mt7621.h > * ralink_regs.h > > This is because this path is directly included in > arch/mips/ralink/Platform for "ralink": > > # > # Ralink SoC common stuff > # > cflags-$(CONFIG_RALINK) += -I$(srctree)/arch/mips/include/asm/mach-ralink > > and this driver directly depends on RALINK or COMPILE_TEST (which > might be the problem here): > > > and this driver directly depends > on RALINK or COMPILE_TEST: > > config PHY_MT7621_PCI > tristate "MediaTek MT7621 PCI PHY Driver" > depends on (RALINK || COMPILE_TEST) && OF > select GENERIC_PHY > select REGMAP_MMIO > help > Say 'Y' here to add support for MediaTek MT7621 PCI PHY driver > > > > > I have reverted that commit for today. > > What is the correct way of fixing this? Include complete path for both > of them like this? > > index db79088d5362..cebd53f5a797 100644 > --- a/drivers/phy/ralink/phy-mt7621-pci.c > +++ b/drivers/phy/ralink/phy-mt7621-pci.c > @@ -14,8 +14,8 @@ > #include > #include > #include > -#include > -#include > +#include > +#include > > Vinod, please let me know if you want me to send anything for fixing this. Yes this makes sense. this will ensure it gets picked up and doesn't depend in arch specific stuff -- ~Vinod