All of lore.kernel.org
 help / color / mirror / Atom feed
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, linux-next@vger.kernel.org,
	linux-alpha@vger.kernel.org,
	Richard Henderson <richard.henderson@linaro.org>,
	Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
	Matt Turner <mattst88@gmail.com>
Subject: build failure of next-20220818 due to 81c0386c1376 ("regmap: mmio: Support accelerared noinc operations")
Date: Thu, 18 Aug 2022 12:24:54 +0100	[thread overview]
Message-ID: <Yv4hhoTTcRuk/2Kl@debian> (raw)

Hi All,

Not sure if it has been reported, builds of alpha allmodconfig have
failed to build next-20220818 with the error:

drivers/base/regmap/regmap-mmio.c: In function 'regmap_mmio_noinc_write':
drivers/base/regmap/regmap-mmio.c:221:17: error: implicit declaration of function 'writesb'; did you mean 'writeb'? [-Werror=implicit-function-declaration]
  221 |                 writesb(ctx->regs + reg, (const u8 *)val, val_count);
      |                 ^~~~~~~
      |                 writeb
drivers/base/regmap/regmap-mmio.c:224:17: error: implicit declaration of function 'writesw'; did you mean 'writew'? [-Werror=implicit-function-declaration]
  224 |                 writesw(ctx->regs + reg, (const u16 *)val, val_count);
      |                 ^~~~~~~
      |                 writew
drivers/base/regmap/regmap-mmio.c:227:17: error: implicit declaration of function 'writesl'; did you mean 'writel'? [-Werror=implicit-function-declaration]
  227 |                 writesl(ctx->regs + reg, (const u32 *)val, val_count);
      |                 ^~~~~~~
      |                 writel
drivers/base/regmap/regmap-mmio.c:231:17: error: implicit declaration of function 'writesq'; did you mean 'writeq'? [-Werror=implicit-function-declaration]
  231 |                 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")
And, reverting that commit has fixed the build failure.

I will be happy to test any patch or provide any extra log if needed.


--
Regards
Sudip

             reply	other threads:[~2022-08-18 11:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-18 11:24 Sudip Mukherjee (Codethink) [this message]
2022-08-18 20:55 ` build failure of next-20220818 due to 81c0386c1376 ("regmap: mmio: Support accelerared noinc operations") Linus Walleij

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=Yv4hhoTTcRuk/2Kl@debian \
    --to=sudipm.mukherjee@gmail.com \
    --cc=broonie@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=ink@jurassic.park.msu.ru \
    --cc=linus.walleij@linaro.org \
    --cc=linux-alpha@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mattst88@gmail.com \
    --cc=rafael@kernel.org \
    --cc=richard.henderson@linaro.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.