From: Vinod Koul <vkoul@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Peter Ujfalusi <peter.ujfalusi@gmail.com>,
dmaengine@vger.kernel.org
Subject: Re: linux-next: Tree for May 15 (drivers/dma/ti/k3-udma.c)
Date: Tue, 16 May 2023 23:05:56 +0530 [thread overview]
Message-ID: <ZGO+/E34V83rjQKi@matsya> (raw)
In-Reply-To: <abc2472d-34f1-069b-00c8-66b751158fa9@infradead.org>
On 15-05-23, 19:18, Randy Dunlap wrote:
> Hi--
>
> On 5/14/23 21:12, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20230512:
> >
> > New trees: fastrpc, wpan-staging
> >
>
> This build problem has been around for a few days/weeks/?.
>
> # CONFIG_SUSPEND is not set
>
> ../drivers/dma/ti/k3-udma.c:5552:12: warning: 'udma_pm_resume' defined but not used [-Wunused-function]
> 5552 | static int udma_pm_resume(struct device *dev)
> | ^~~~~~~~~~~~~~
> ../drivers/dma/ti/k3-udma.c:5530:12: warning: 'udma_pm_suspend' defined but not used [-Wunused-function]
> 5530 | static int udma_pm_suspend(struct device *dev)
> | ^~~~~~~~~~~~~~~
Thanks for report, this should be fixed by adding __maybe_unused. I will
send a patch shortly
--
~Vinod
next prev parent reply other threads:[~2023-05-16 17:36 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 4:12 linux-next: Tree for May 15 Stephen Rothwell
2023-05-16 2:18 ` linux-next: Tree for May 15 (drivers/dma/ti/k3-udma.c) Randy Dunlap
2023-05-16 17:35 ` Vinod Koul [this message]
2023-05-16 2:23 ` linux-next: Tree for May 15 (net/ipv4/ipconfig.c:) Randy Dunlap
2023-05-18 3:57 ` David Ahern
2023-05-16 2:26 ` linux-next: Tree for May 15 (drivers/macintosh/ams/ams-core.c) Randy Dunlap
2023-05-16 2:40 ` linux-next: Tree for May 15 (drivers/tty/serial/8250/8250_omap.c) Randy Dunlap
2023-05-17 5:51 ` Tony Lindgren
2023-05-16 2:45 ` linux-next: Tree for May 15 (several RV64 build errors) Randy Dunlap
2023-05-16 6:18 ` Alexandre Ghiti
2023-05-19 10:42 ` Alexandre Ghiti
2023-05-19 11:22 ` Conor Dooley
2023-05-19 12:09 ` Alexandre Ghiti
2023-05-23 2:28 ` Randy Dunlap
2023-05-23 13:07 ` Alexandre Ghiti
2023-05-24 0:22 ` Randy Dunlap
2023-05-24 1:29 ` Palmer Dabbelt
2023-05-24 6:23 ` Arnd Bergmann
2023-05-24 22:41 ` Randy Dunlap
2023-05-24 22:49 ` Conor Dooley
2023-05-24 23:11 ` Palmer Dabbelt
2023-05-25 12:50 ` Conor Dooley
2023-05-16 2:51 ` linux-next: Tree for May 15 (config SERIAL_CPM) Randy Dunlap
2023-05-18 5:49 ` Jiri Slaby
2023-05-18 5:50 ` Jiri Slaby
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=ZGO+/E34V83rjQKi@matsya \
--to=vkoul@kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=peter.ujfalusi@gmail.com \
--cc=rdunlap@infradead.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