public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Rob Herring <robh@kernel.org>,
	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: Tue, 10 Oct 2023 12:29:15 +0530	[thread overview]
Message-ID: <ZST2Q1khDtCtADBs@matsya> (raw)
In-Reply-To: <20231010145412.4a758f9d@canb.auug.org.au>

On 10-10-23, 14:54, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the dmaengine tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
> 
> drivers/dma/mmp_tdma.c: In function 'mmp_tdma_probe':
> drivers/dma/mmp_tdma.c:638:36: error: unused variable 'of_id' [-Werror=unused-variable]
>   638 |         const struct of_device_id *of_id;
>       |                                    ^~~~~
> cc1: all warnings being treated as errors
> 
> Caused by commit
> 
>   a67ba97dfb30 ("dmaengine: Use device_get_match_data()")
> 
> I have used the dmaengine tree from next-20231009 for today.

Thanks for the report, I have posted the fix:
https://lore.kernel.org/dmaengine/20231010065729.29385-1-vkoul@kernel.org/

-- 
~Vinod

  reply	other threads:[~2023-10-10  6:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-10  3:54 linux-next: build failure after merge of the dmaengine tree Stephen Rothwell
2023-10-10  6:59 ` Vinod Koul [this message]
2023-10-11 13:41 ` Rob Herring
2023-10-12 12:30   ` Vinod Koul
  -- strict thread matches above, loose matches on Subject: below --
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=ZST2Q1khDtCtADBs@matsya \
    --to=vkoul@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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