From: Troy Mitchell <troy.mitchell@linux.dev>
To: Encrow Thorne <jyc0019@gmail.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
Troy Mitchell <troy.mitchell@linux.dev>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] reset: fix BIT macro reference
Date: Thu, 6 Nov 2025 00:19:12 +0800 [thread overview]
Message-ID: <aQt5AAj1DPv4L_ri@troy-wujie14pro-arch> (raw)
In-Reply-To: <20251105-rfc-reset-include-bits-v2-1-f27c57b75a90@gmail.com>
On Wed, Nov 05, 2025 at 11:40:12PM +0800, Encrow Thorne wrote:
> RESET_CONTROL_FLAGS_BIT_* macros use BIT(), but reset.h does not
> include bits.h or bitops.h. This causes compilation errors when
> including reset.h standalone.
>
> Include bits.h to make reset.h self-contained.
>
> Suggested-by: Troy Mitchell <troy.mitchell@linux.dev>
> Reviewed-by: Troy Mitchell <troy.mitchell@linux.dev>
> Signed-off-by: Encrow Thorne <jyc0019@gmail.com>
> ---
> Changes in v2:
> - EDITME: describe what is new in this series revision.
> - EDITME: use bulletpoints and terse descriptions.
> - Link to v1: https://lore.kernel.org/r/20251105-rfc-reset-include-bits-v1-1-d7e1bbc7e1ab@gmail.com
What's that?
- Troy
> ---
> include/linux/reset.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/include/linux/reset.h b/include/linux/reset.h
> index 840d75d172f6..44f9e3415f92 100644
> --- a/include/linux/reset.h
> +++ b/include/linux/reset.h
> @@ -2,6 +2,7 @@
> #ifndef _LINUX_RESET_H_
> #define _LINUX_RESET_H_
>
> +#include <linux/bits.h>
> #include <linux/err.h>
> #include <linux/errno.h>
> #include <linux/types.h>
>
> ---
> base-commit: 8fec172c82c2b5f6f8e47ab837c1dc91ee3d1b87
> change-id: 20251105-rfc-reset-include-bits-4ec72344d1a3
>
> Best regards,
> --
> Encrow Thorne <jyc0019@gmail.com>
>
prev parent reply other threads:[~2025-11-05 16:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-05 15:40 Encrow Thorne
2025-11-05 15:51 ` Philipp Zabel
2025-11-05 17:00 ` Encrow Thorne
2025-11-10 5:58 ` Troy Mitchell
2025-11-05 16:19 ` Troy Mitchell [this message]
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=aQt5AAj1DPv4L_ri@troy-wujie14pro-arch \
--to=troy.mitchell@linux.dev \
--cc=jyc0019@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
/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
all inboxes | Powered by JetHome®