Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <YtH53r9UcYwquxcx@debian> <043cec12-b719-e9e6-d234-fe6ca75ca894@gmail.com>
 <a15dc5d9-ed10-d75b-3e76-e5e03ebfe25f@sholland.org>
In-Reply-To: <a15dc5d9-ed10-d75b-3e76-e5e03ebfe25f@sholland.org>
From:   Linus Walleij <linus.walleij@linaro.org>
Date:   Mon, 18 Jul 2022 11:41:25 +0200
Message-ID: <CACRpkdZ6yPUd0KPLqviB_ufiEe9dz3XyP+JPkP5ujKc7xYYKVw@mail.gmail.com>
Subject: Re: build failure of next-20220715 due to "No rule to make target"
To:     Samuel Holland <samuel@sholland.org>
Cc:     Florian Fainelli <f.fainelli@gmail.com>,
        "Sudip Mukherjee (Codethink)" <sudipm.mukherjee@gmail.com>,
        Chen-Yu Tsai <wens@csie.org>,
        Jernej Skrabec <jernej.skrabec@gmail.com>,
        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
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Sat, Jul 16, 2022 at 4:15 AM Samuel Holland <samuel@sholland.org> wrote:

> The patch in question[0] contains the new file, so something must have gone
> wrong when applying it[1].

Patch 6/6 didn't apply cleanly so was applied with
patch -p1 < patch.patch and then I missed to git add the .c file.

> I wasn't sure what to do, so I resent the whole
> series[2], in case the index hashes in the v1 patches were causing the problem.

Fixed up by applying v2 now!

Linus Walleij