From: Vinod Koul <vkoul@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "Martin Povišer" <povik+lin@cutebit.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: Fri, 10 Jun 2022 10:02:32 +0530 [thread overview]
Message-ID: <YqLJYJglqmDnGZGP@matsya> (raw)
In-Reply-To: <20220610124626.141d5f61@canb.auug.org.au>
On 10-06-22, 12:46, Stephen Rothwell wrote:
> Hi all,
>
> After merging the dmaengine tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> In file included from include/linux/printk.h:584,
> from include/linux/kernel.h:29,
> from arch/x86/include/asm/percpu.h:27,
> from arch/x86/include/asm/current.h:6,
> from include/linux/sched.h:12,
> from include/linux/ratelimit.h:6,
> from include/linux/dev_printk.h:16,
> from include/linux/device.h:15,
> from drivers/dma/apple-admac.c:10:
> drivers/dma/apple-admac.c: In function 'admac_cyclic_write_one_desc':
> drivers/dma/apple-admac.c:209:26: error: format '%x' expects argument of type 'unsigned int', but argument 7 has type 'long unsigned int' [-Werror=format=]
> 209 | dev_dbg(ad->dev, "ch%d descriptor: addr=0x%pad len=0x%zx flags=0x%x\n",
Thanks for the report, I have fixed it up and send the patch to fix the
print format
https://lore.kernel.org/dmaengine/20220610043117.39337-1-vkoul@kernel.org/
--
~Vinod
next prev parent reply other threads:[~2022-06-10 4:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 2:46 linux-next: build failure after merge of the dmaengine tree Stephen Rothwell
2022-06-10 4:32 ` Vinod Koul [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-09-04 18:11 Mark Brown
2026-09-07 9:07 ` Vinod Koul
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
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=YqLJYJglqmDnGZGP@matsya \
--to=vkoul@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=povik+lin@cutebit.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.