From: Florian Fainelli <f.fainelli@gmail.com>
To: "Sudip Mukherjee (Codethink)" <sudipm.mukherjee@gmail.com>,
Linus Walleij <linus.walleij@linaro.org>,
Chen-Yu Tsai <wens@csie.org>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Samuel Holland <samuel@sholland.org>
Cc: linux-gpio@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-sunxi@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-next@vger.kernel.org
Subject: Re: build failure of next-20220715 due to "No rule to make target"
Date: Fri, 15 Jul 2022 18:59:12 -0700 [thread overview]
Message-ID: <043cec12-b719-e9e6-d234-fe6ca75ca894@gmail.com> (raw)
In-Reply-To: <YtH53r9UcYwquxcx@debian>
On 7/15/2022 4:35 PM, Sudip Mukherjee (Codethink) wrote:
> Hi All,
>
> Not sure if it has been reported, builds of arm and arm64 allmodconfig
> have failed to build next-20220715 with the error:
>
> make[3]: *** No rule to make target 'drivers/pinctrl/sunxi/pinctrl-sun20i-d1.o', needed by 'drivers/pinctrl/sunxi/built-in.a'. Stop.
Caused by f6e42a0fce98b85380df8cdfb081d75c48e4fee1 ("pinctrl: sunxi: Add
driver for Allwinner D1/D1s") adding CONFIG_PINCTRL_SUN20I_D1 a build
rule in drivers/pinctrl/sunxi/Makefile to build pinctrl-sun20i-d1.o but
... there was no drivers/pinctrl/sunxi/pinctrl-sun20i-d1.c file added to
the commit, missing git add presumably?
--
Florian
next prev parent reply other threads:[~2022-07-16 1:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-15 23:35 build failure of next-20220715 due to "No rule to make target" Sudip Mukherjee (Codethink)
2022-07-16 1:59 ` Florian Fainelli [this message]
2022-07-16 2:15 ` Samuel Holland
2022-07-18 9:41 ` Linus Walleij
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=043cec12-b719-e9e6-d234-fe6ca75ca894@gmail.com \
--to=f.fainelli@gmail.com \
--cc=jernej.skrabec@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=samuel@sholland.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=wens@csie.org \
/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