From: "Michael Walle" <mwalle@kernel.org>
To: "Nathan Chancellor" <nathan@kernel.org>,
"Lee Jones" <lee@kernel.org>, "Job Sava" <jsava@criticallink.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mfd: tps6594: Explicitly include bitfield.h
Date: Fri, 05 Sep 2025 08:38:31 +0200 [thread overview]
Message-ID: <DCKNRRN0Q2I7.WFT5U4QKA9XS@kernel.org> (raw)
In-Reply-To: <20250904-mfd-tps6594-core-fix-bitfield-h-v1-1-5d0f00cfe58f@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1195 bytes --]
Hi Nathan,
On Fri Sep 5, 2025 at 3:26 AM CEST, Nathan Chancellor wrote:
> After a recent change that started using FIELD_GET() in tps6594-core.c,
> there is an error when bitfield.h is not implicitly included, such as
> when building allmodconfig for ARCH=hexagon:
Thanks! I was already in a discussion with Lee about how to handle
that.
> drivers/mfd/tps6594-core.c:767:7: error: call to undeclared function 'FIELD_GET'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
> 767 | if (FIELD_GET(TPS65224_MASK_EN_PB_VSENSE_CONFIG, pwr_on) == TPS65224_EN_SEL_PB ||
> | ^
>
> Explicitly include bitfield.h to resolve the errors.
>
> Fixes: d766ca01c208 ("mfd: tps6594: Add power button functionality")
> Signed-off-by: Nathan Chancellor <nathan@kernel.org>
In any case:
Reviewed-by: Michael Walle <mwalle@kernel.org>
Also,
Reported-by: kernel test robot <lkp@intel.com>
Closes: https://lore.kernel.org/oe-kbuild-all/202509032356.LGa5hygM-lkp@intel.com/
> ---
> It looks like this should go into ib-mfd-input-6.18.
Yeah probably. Lee, is that possible?
-michael
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 297 bytes --]
next prev parent reply other threads:[~2025-09-05 6:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-05 1:26 [PATCH] mfd: tps6594: Explicitly include bitfield.h Nathan Chancellor
2025-09-05 6:38 ` Michael Walle [this message]
2025-09-11 15:11 ` Lee Jones
2025-09-11 15:15 ` Lee Jones
2025-09-11 15:10 ` (subset) " Lee Jones
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=DCKNRRN0Q2I7.WFT5U4QKA9XS@kernel.org \
--to=mwalle@kernel.org \
--cc=jsava@criticallink.com \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nathan@kernel.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