Linux-Next discussions
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Srini Kandagatla <srinivas.kandagatla@linaro.org>,
	Ekansh Gupta <ekansh.gupta@oss.qualcomm.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build failure after merge of the fastrpc tree
Date: Sun, 26 Jul 2026 23:42:40 +0100	[thread overview]
Message-ID: <amaNYEchEvJAcnQT@sirena.org.uk> (raw)

[-- Attachment #1: Type: text/plain, Size: 3078 bytes --]

Hi all,

After merging the fastrpc tree, today's linux-next build (x86_64
allmodconfig) failed like this:

/tmp/next/build/drivers/misc/fastrpc.c:599:29: error: call to undeclared function 'FIELD_GET'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
  599 |         idr_remove(&cctx->ctx_idr, FIELD_GET(FASTRPC_CTXID_MASK, ctx->ctxid));
      |                                    ^
/tmp/next/build/drivers/misc/fastrpc.c:737:15: error: call to undeclared function 'FIELD_PREP'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
  737 |         ctx->ctxid = FIELD_PREP(FASTRPC_CTXID_MASK, ret) |
      |                      ^
/tmp/next/build/drivers/misc/fastrpc.c:2711:10: error: call to undeclared function 'FIELD_GET'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
 2711 |         ctxid = FIELD_GET(FASTRPC_CTXID_MASK, rsp->ctx);
      |                 ^
/tmp/next/build/drivers/misc/fastrpc.c:2735:4: error: format specifies type 'unsigned long long' but the argument has type 'int' [-Werror,-Wformat]
 2733 |                         "Stale glink response ctx 0x%llx (expected seq 0x%llx), dropping\n",
      |                                                                          ~~~~
      |                                                                          %x
 2734 |                         rsp->ctx,
 2735 |                         FIELD_GET(FASTRPC_CTXID_SEQ_MASK, ctx->ctxid));
      |                         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/tmp/next/build/include/linux/dev_printk.h:165:39: note: expanded from macro 'dev_dbg'
  165 |         dynamic_dev_dbg(dev, dev_fmt(fmt), ##__VA_ARGS__)
      |                                      ~~~     ^~~~~~~~~~~
/tmp/next/build/include/linux/dynamic_debug.h:285:19: note: expanded from macro 'dynamic_dev_dbg'
  285 |                            dev, fmt, ##__VA_ARGS__)
      |                                 ~~~    ^~~~~~~~~~~
/tmp/next/build/include/linux/dynamic_debug.h:261:59: note: expanded from macro '_dynamic_func_call'
  261 |         _dynamic_func_call_cls(_DPRINTK_CLASS_DFLT, fmt, func, ##__VA_ARGS__)
      |                                                                  ^~~~~~~~~~~
/tmp/next/build/include/linux/dynamic_debug.h:259:65: note: expanded from macro '_dynamic_func_call_cls'
  259 |         __dynamic_func_call_cls(__UNIQUE_ID(ddebug), cls, fmt, func, ##__VA_ARGS__)
      |                                                                        ^~~~~~~~~~~
/tmp/next/build/include/linux/dynamic_debug.h:231:15: note: expanded from macro '__dynamic_func_call_cls'
  231 |                 func(&id, ##__VA_ARGS__);                       \
      |                             ^~~~~~~~~~~
4 errors generated.


Caused by commit

  10555ba6126ed (misc: fastrpc: Replace hardcoded ctxid mask with GENMASK)

(and one of the subsequent ones that also uses those macros).  I have
use the tree from next-20260723 instead.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

                 reply	other threads:[~2026-07-26 22:42 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=amaNYEchEvJAcnQT@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=ekansh.gupta@oss.qualcomm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=srinivas.kandagatla@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox