From: Vinod Koul <vkoul@kernel.org>
To: Sergio Paracuellos <sergio.paracuellos@gmail.com>
Cc: kishon@ti.com, linux-kernel@vger.kernel.org, linux-next@vger.kernel.org
Subject: Re: [PATCH v3 0/2] phy: ralink: phy-mt7621-pci: some fixes for COMPILE_TEST
Date: Tue, 1 Dec 2020 17:14:53 +0530 [thread overview]
Message-ID: <20201201114453.GC8403@vkoul-mobl> (raw)
In-Reply-To: <20201201112051.17463-1-sergio.paracuellos@gmail.com>
On 01-12-20, 12:20, Sergio Paracuellos wrote:
> Hi Vinod,
>
> 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 <mt7621.h>
> | ^~~~~~~~~~
>
> 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".
>
> Adding the include search path to the phy ralink directory fix the problem but
> as you told me I finally end up removing COMPILE_TEST from Kconfig.
>
> Making 'allmodconfig' in x86_64 also showed two warnings for this driver
> because of pointer size and not valid name for MODULE_DEVICE_TABLE ids.
>
> Ids for the macro has been also included in this series.
Applied, thanks
--
~Vinod
next prev parent reply other threads:[~2020-12-01 11:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-01 11:20 [PATCH v3 0/2] phy: ralink: phy-mt7621-pci: some fixes for COMPILE_TEST Sergio Paracuellos
2020-12-01 11:20 ` [PATCH v3 1/2] phy: ralink: phy-mt7621-pci: drop 'COMPILE_TEST' from Kconfig Sergio Paracuellos
2020-12-01 11:20 ` [PATCH v3 2/2] phy: ralink: phy-mt7621-pci: set correct name in MODULE_DEVICE_TABLE macro Sergio Paracuellos
2020-12-01 11:44 ` Vinod Koul [this message]
2020-12-01 11:57 ` [PATCH v3 0/2] phy: ralink: phy-mt7621-pci: some fixes for COMPILE_TEST Sergio Paracuellos
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201201114453.GC8403@vkoul-mobl \
--to=vkoul@kernel.org \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sergio.paracuellos@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox