From: "Sudip Mukherjee (Codethink)" <sudipm.mukherjee@gmail.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Mark Brown <broonie@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: mainline build failure due to 81c0386c1376 ("regmap: mmio: Support accelerared noinc operations")
Date: Wed, 5 Oct 2022 07:30:56 +0100 [thread overview]
Message-ID: <Yz0koHybNXGTFfDr@debian> (raw)
Hi All,
The latest mainline kernel branch fails to build alpha allmodconfig
with the error:
drivers/base/regmap/regmap-mmio.c: In function 'regmap_mmio_noinc_write':
drivers/base/regmap/regmap-mmio.c:222:17: error: implicit declaration of function 'writesb'; did you mean 'writeb'? [-Werror=implicit-function-declaration]
222 | writesb(ctx->regs + reg, (const u8 *)val, val_count);
| ^~~~~~~
| writeb
drivers/base/regmap/regmap-mmio.c:225:17: error: implicit declaration of function 'writesw'; did you mean 'writew'? [-Werror=implicit-function-declaration]
225 | writesw(ctx->regs + reg, (const u16 *)val, val_count);
| ^~~~~~~
| writew
drivers/base/regmap/regmap-mmio.c:228:17: error: implicit declaration of function 'writesl'; did you mean 'writel'? [-Werror=implicit-function-declaration]
228 | writesl(ctx->regs + reg, (const u32 *)val, val_count);
| ^~~~~~~
| writel
drivers/base/regmap/regmap-mmio.c:232:17: error: implicit declaration of function 'writesq'; did you mean 'writeq'? [-Werror=implicit-function-declaration]
232 | writesq(ctx->regs + reg, (const u64 *)val, val_count);
| ^~~~~~~
| writeq
drivers/base/regmap/regmap-mmio.c: In function 'regmap_mmio_noinc_read':
drivers/base/regmap/regmap-mmio.c:358:17: error: implicit declaration of function 'readsb'; did you mean 'readb'? [-Werror=implicit-function-declaration]
358 | readsb(ctx->regs + reg, (u8 *)val, val_count);
| ^~~~~~
| readb
drivers/base/regmap/regmap-mmio.c:361:17: error: implicit declaration of function 'readsw'; did you mean 'readw'? [-Werror=implicit-function-declaration]
361 | readsw(ctx->regs + reg, (u16 *)val, val_count);
| ^~~~~~
| readw
drivers/base/regmap/regmap-mmio.c:364:17: error: implicit declaration of function 'readsl'; did you mean 'readl'? [-Werror=implicit-function-declaration]
364 | readsl(ctx->regs + reg, (u32 *)val, val_count);
| ^~~~~~
| readl
drivers/base/regmap/regmap-mmio.c:368:17: error: implicit declaration of function 'readsq'; did you mean 'readq'? [-Werror=implicit-function-declaration]
368 | readsq(ctx->regs + reg, (u64 *)val, val_count);
| ^~~~~~
| readq
git bisect pointed to 81c0386c1376 ("regmap: mmio: Support accelerared noinc operations")
I will be happy to test any patch or provide any extra log if needed.
Note:
Already reported for next-20220818 at https://lore.kernel.org/lkml/Yv4hhoTTcRuk%2F2Kl@debian/
--
Regards
Sudip
next reply other threads:[~2022-10-05 6:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-05 6:30 Sudip Mukherjee (Codethink) [this message]
2022-10-05 10:38 ` mainline build failure due to 81c0386c1376 ("regmap: mmio: Support accelerared noinc operations") Mark Brown
2022-10-05 20:04 ` Linus Walleij
2022-10-06 19:13 ` Linus Torvalds
2022-10-06 19:47 ` Sudip Mukherjee
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=Yz0koHybNXGTFfDr@debian \
--to=sudipm.mukherjee@gmail.com \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=torvalds@linux-foundation.org \
/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.