From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Sudeep Holla <sudeep.holla@arm.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 scmi tree
Date: Fri, 6 Oct 2023 10:39:29 +1100 [thread overview]
Message-ID: <20231006103929.4c56edb3@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1153 bytes --]
Hi all,
After merging the scmi tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
In file included from drivers/tee/optee/ffa_abi.c:8:
include/linux/arm_ffa.h: In function 'ffa_mem_desc_offset':
include/linux/arm_ffa.h:105:10: error: implicit declaration of function 'FIELD_PREP' [-Werror=implicit-function-declaration]
105 | (FIELD_PREP(FFA_MAJOR_VERSION_MASK, (major)) | \
| ^~~~~~~~~~
include/linux/arm_ffa.h:107:33: note: in expansion of macro 'FFA_PACK_VERSION_INFO'
107 | #define FFA_VERSION_1_0 FFA_PACK_VERSION_INFO(1, 0)
| ^~~~~~~~~~~~~~~~~~~~~
include/linux/arm_ffa.h:368:28: note: in expansion of macro 'FFA_VERSION_1_0'
368 | if (ffa_version <= FFA_VERSION_1_0)
| ^~~~~~~~~~~~~~~
Exposed by commit
0624de756f75 ("firmware: arm_ffa: Update memory descriptor to support v1.1 format")
This has been possible for a while, and arm_ffa.h needs to include
linus/bitfoeld.h ...
I have used the scmi tree from next-20231005 for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2023-10-05 23:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-05 23:39 Stephen Rothwell [this message]
2023-10-06 6:50 ` linux-next: build failure after merge of the scmi tree Sudeep Holla
-- strict thread matches above, loose matches on Subject: below --
2023-11-30 21:59 Stephen Rothwell
2023-11-30 22:01 ` Sudeep Holla
2022-11-08 22:29 Stephen Rothwell
2022-11-09 8:58 ` Sudeep Holla
2022-07-01 0:36 Stephen Rothwell
2022-07-01 8:13 ` Sudeep Holla
2020-07-08 23:58 Stephen Rothwell
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=20231006103929.4c56edb3@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sudeep.holla@arm.com \
/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;
as well as URLs for NNTP newsgroup(s).