From: Karthik B S <karthik.b.s@intel.com>
To: Ankit Nautiyal <ankit.k.nautiyal@intel.com>,
<igt-dev@lists.freedesktop.org>
Cc: <kamil.konieczny@linux.intel.com>,
<ville.syrjala@linux.intel.com>, <jani.nikula@linux.intel.com>
Subject: Re: [PATCH i-g-t 1/8] include/linux_scaffold: Add BIT_U{8,16,32} macros
Date: Tue, 28 Apr 2026 14:34:30 +0530 [thread overview]
Message-ID: <023dcba0-b694-49f2-9fcb-e8c4ac8f3007@intel.com> (raw)
In-Reply-To: <20260427124607.3115567-2-ankit.k.nautiyal@intel.com>
On 4/27/2026 6:16 PM, Ankit Nautiyal wrote:
> Add macros to accommodate the kernel macros BIT_U8, BIT_U16, BIT_U32
> in the header file `intel_vbt_defs.h` copied from the kernel.
>
> v2: Add BIT_U64 for completeness. (Karthik)
>
> Signed-off-by: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
Reviewed-by: Karthik B S <karthik.b.s@intel.com>
> ---
> include/linux_scaffold.h | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/include/linux_scaffold.h b/include/linux_scaffold.h
> index 281aa5e730ed..0c970c86079a 100644
> --- a/include/linux_scaffold.h
> +++ b/include/linux_scaffold.h
> @@ -57,4 +57,9 @@ static inline s64 sign_extend64(u64 value, int index)
> #define FIELD_GET(mask, reg) \
> (typeof(mask))(((reg) & (mask)) >> __bf_shf(mask))
>
> +#define BIT_U8(n) ((u8)(1U << (n)))
> +#define BIT_U16(n) ((u16)(1U << (n)))
> +#define BIT_U32(n) ((u32)(1U << (n)))
> +#define BIT_U64(n) ((u64)(1ULL << (n)))
> +
> #endif /* _INTEL_GPU_COMMANDS_SCAFFOLD_H_ */
next prev parent reply other threads:[~2026-04-28 9:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-27 12:45 [PATCH i-g-t 0/8] intel_vbt_decode: Sync intel_vbt_defs.h with latest changes Ankit Nautiyal
2026-04-27 12:46 ` [PATCH i-g-t 1/8] include/linux_scaffold: Add BIT_U{8,16,32} macros Ankit Nautiyal
2026-04-28 9:04 ` Karthik B S [this message]
2026-04-27 12:46 ` [PATCH i-g-t 2/8] tools/intel_vbt_decode.c: Include linux_scaffold.h Ankit Nautiyal
2026-04-27 12:46 ` [PATCH i-g-t 3/8] tools/intel_vbt_defs: sync intel_vbt_defs.h with kernel commit 4d33c77cf2c3 Ankit Nautiyal
2026-04-27 12:46 ` [PATCH i-g-t 4/8] tools/intel_vbt_defs: sync intel_vbt_defs.h with kernel commit 203c7904f2d8 Ankit Nautiyal
2026-04-27 12:46 ` [PATCH i-g-t 5/8] tools/intel_vbt_defs: sync intel_vbt_defs.h with kernel commit 1b85a9b04681 Ankit Nautiyal
2026-04-27 14:41 ` Kamil Konieczny
2026-04-28 3:57 ` Nautiyal, Ankit K
2026-04-28 8:32 ` Kamil Konieczny
2026-04-27 12:46 ` [PATCH i-g-t 6/8] tools/intel_vbt_decode: dump eDP data rate override field Ankit Nautiyal
2026-04-27 12:46 ` [PATCH i-g-t 7/8] tools/intel_vbt_decode: dump eDP joiner enable field Ankit Nautiyal
2026-04-27 12:46 ` [PATCH i-g-t 8/8] tools/intel_vbt_decode: Dump dedicated_external and dyn_port_over_tc fields Ankit Nautiyal
2026-04-27 22:39 ` ✓ i915.CI.BAT: success for intel_vbt_decode: Sync intel_vbt_defs.h with latest changes (rev6) Patchwork
2026-04-27 23:42 ` ✓ Xe.CI.BAT: " Patchwork
2026-04-28 5:04 ` ✗ i915.CI.Full: failure " Patchwork
2026-04-28 6:10 ` ✗ Xe.CI.FULL: " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2026-04-22 3:43 [PATCH i-g-t 0/8] intel_vbt_decode: Sync intel_vbt_defs.h with latest changes Ankit Nautiyal
2026-04-22 3:43 ` [PATCH i-g-t 1/8] include/linux_scaffold: Add BIT_U{8,16,32} macros Ankit Nautiyal
2026-04-27 5:07 ` Karthik B S
2026-04-27 12:31 ` Nautiyal, Ankit K
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=023dcba0-b694-49f2-9fcb-e8c4ac8f3007@intel.com \
--to=karthik.b.s@intel.com \
--cc=ankit.k.nautiyal@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=kamil.konieczny@linux.intel.com \
--cc=ville.syrjala@linux.intel.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