From: Vinod Koul <vkoul@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
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: Thu, 12 Oct 2023 18:00:11 +0530 [thread overview]
Message-ID: <ZSfm0wDCFD9cewrS@matsya> (raw)
In-Reply-To: <CAL_JsqJkEutiwWdNe336pWbcLsHK9tNxHNYVOAACt_ncaBdBXQ@mail.gmail.com>
On 11-10-23, 08:41, Rob Herring wrote:
> On Mon, Oct 9, 2023 at 10:54 PM Stephen Rothwell <sfr@canb.auug.org.au> 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()")
>
> FWIW, my patch has the above line removed. Seems it got dropped when applying.
Looks like it got missed while applying the patch. The patch had a
conflict so I had to manually apply this one...
Sorry to have missed that
--
~Vinod
next prev parent reply other threads:[~2023-10-12 12:30 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
2023-10-11 13:41 ` Rob Herring
2023-10-12 12:30 ` Vinod Koul [this message]
-- 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=ZSfm0wDCFD9cewrS@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 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.