From: Vinod Koul <vkoul@kernel.org>
To: "Toralf Förster" <toralf.foerster@gmx.de>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>, dmaengine@vger.kernel.org
Subject: Re: compile error for 5.15.4
Date: Sun, 21 Nov 2021 22:28:49 +0530 [thread overview]
Message-ID: <YZp6yfVUx4eEwaxm@matsya> (raw)
In-Reply-To: <747802b9-6c5d-cdb5-66e2-05b820f5213c@gmx.de>
Hello,
On 21-11-21, 16:02, Toralf Förster wrote:
> Hi,
>
> got this at a hardened stable Gentoo Server:
>
> # uname -a
> Linux mr-fox 5.14.17 #1 SMP Thu Nov 18 14:02:58 CET 2021 x86_64 AMD
> Ryzen 9 5950X 16-Core Processor AuthenticAMD GNU/Linux
>
>
> CC net/ipv4/tcp_timer.o
> CC lib/raid6/sse1.o
> drivers/dma/ptdma/ptdma-debugfs.c: In function ‘ptdma_debugfs_setup’:
> drivers/dma/ptdma/ptdma-debugfs.c:93:54: error: ‘struct dma_device’ has
> no member named ‘dbg_dev_root’
> 93 | debugfs_create_file("info", 0400,
> pt->dma_dev.dbg_dev_root, pt,
Can you please send your config file when you saw this, which toolchain
was used to compile...
Thanks
> | ^
> drivers/dma/ptdma/ptdma-debugfs.c:96:55: error: ‘struct dma_device’ has
> no member named ‘dbg_dev_root’
> 96 | debugfs_create_file("stats", 0400,
> pt->dma_dev.dbg_dev_root, pt,
> | ^
> drivers/dma/ptdma/ptdma-debugfs.c:102:52: error: ‘struct dma_device’ has
> no member named ‘dbg_dev_root’
> 102 | debugfs_create_dir("q", pt->dma_dev.dbg_dev_root);
> | ^
> make[3]: *** [scripts/Makefile.build:277:
> drivers/dma/ptdma/ptdma-debugfs.o] Error 1
> make[2]: *** [scripts/Makefile.build:540: drivers/dma/ptdma] Error 2
> make[1]: *** [scripts/Makefile.build:540: drivers/dma] Error 2
> make[1]: *** Waiting for unfinished jobs....
> CC mm/usercopy.o
> CC lib/argv_split.o
>
> --
> Toralf
--
~Vinod
next prev parent reply other threads:[~2021-11-21 16:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-21 15:02 compile error for 5.15.4 Toralf Förster
2021-11-21 16:58 ` Vinod Koul [this message]
2021-11-21 17:18 ` Toralf Förster
2021-11-22 4:14 ` Vinod Koul
2021-11-22 15:44 ` Toralf Förster
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=YZp6yfVUx4eEwaxm@matsya \
--to=vkoul@kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=toralf.foerster@gmx.de \
/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