From: Vinod Koul <vkoul@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Golla Nagendra <nagendra.golla@amd.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the dmaengine tree
Date: Mon, 7 Sep 2026 14:37:51 +0530 [thread overview]
Message-ID: <ap5-53OJe9XYBM7-@parshuram> (raw)
In-Reply-To: <apsJ089VAvtYHRpP@sirena.co.uk>
On 04-09-26, 19:11, Mark Brown wrote:
> Hi all,
>
> After merging the dmaengine tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> /tmp/next/build/drivers/dma/xilinx/zynqmp_dma.c:1171:1: error: unused label 'err_disable_pm' [-Werror,-Wunused-label]
> 1171 | err_disable_pm:
> | ^~~~~~~~~~~~~~~
>
> Caused by commit
>
> 3f30db282c28c (dmaengine: zynqmp_dma: Fix chan probe/remove error handling)
Yeah I have posted the fix on Friday. It should be in -next tomorrow
> I have used the version from next-20260903 instead.
Thanks
--
~Vinod
next prev parent reply other threads:[~2026-09-07 9:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 18:11 linux-next: build failure after merge of the dmaengine tree Mark Brown
2026-09-07 9:07 ` Vinod Koul [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-10 3:54 Stephen Rothwell
2023-10-10 6:59 ` Vinod Koul
2023-10-11 13:41 ` Rob Herring
2023-10-12 12:30 ` Vinod Koul
2023-09-29 3:13 Stephen Rothwell
2023-10-02 16:09 ` Vinod Koul
2022-06-10 2:46 Stephen Rothwell
2022-06-10 4:32 ` Vinod Koul
2021-10-26 5:06 Stephen Rothwell
2021-10-26 5:07 ` Stephen Rothwell
2021-10-26 5:26 ` Vinod Koul
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=ap5-53OJe9XYBM7-@parshuram \
--to=vkoul@kernel.org \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=nagendra.golla@amd.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.