From: Mithil Bavishi <bavishimithil@gmail•com>
To: nathan@kernel•org
Cc: aaro.koskinen@iki•fi, andreas@kemnade•info,
bavishimithil@gmail•com, kees@kernel•org, khilman@baylibre•com,
linux-arm-kernel@lists•infradead.org,
linux-kernel@vger•kernel.org, linux-omap@vger•kernel.org,
linux@armlinux•org.uk, llvm@lists•linux.dev, rogerq@kernel•org,
samitolvanen@google•com, tony@atomide•com
Subject: Re: [PATCH] ARM: OMAP2+: Make OMAP4 finish_suspend callback CFI-safe
Date: Tue, 12 May 2026 12:53:18 -0400 [thread overview]
Message-ID: <20260512165318.442-1-bavishimithil@gmail.com> (raw)
In-Reply-To: <20260512135757.GB570003@ax162>
> I don't think we have any formal documentation for SYM_TYPED_FUNC_START
> (it should probably be documented via kernel-doc?) but you can read the
> commit message of the change that added it for more information:
>
> e84e008e7b02 ("cfi: Add type helper macros")
Thanks, I had a look at it and other similar commits like
c50d328 ("arm64: Add types to indirect called assembly functions")
I was not aware of SYM_TYPED_FUNC_START before hence the logical approach
was just to wrap the function. But now with this I'll send a v2 with the
ENTRY and ENDPROC changed to SYM_TYPED_FUNC_START and SYM_FUNC_END.
Best,
Mithil
next prev parent reply other threads:[~2026-05-12 16:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 4:23 [PATCH] ARM: OMAP2+: Make OMAP4 finish_suspend callback CFI-safe Mithil Bavishi
2026-05-12 7:34 ` Nathan Chancellor
2026-05-12 8:02 ` Andreas Kemnade
2026-05-12 13:57 ` Nathan Chancellor
2026-05-12 16:53 ` Mithil Bavishi [this message]
2026-05-12 19:05 ` Andreas Kemnade
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=20260512165318.442-1-bavishimithil@gmail.com \
--to=bavishimithil@gmail$(echo .)com \
--cc=aaro.koskinen@iki$(echo .)fi \
--cc=andreas@kemnade$(echo .)info \
--cc=kees@kernel$(echo .)org \
--cc=khilman@baylibre$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-omap@vger$(echo .)kernel.org \
--cc=linux@armlinux$(echo .)org.uk \
--cc=llvm@lists$(echo .)linux.dev \
--cc=nathan@kernel$(echo .)org \
--cc=rogerq@kernel$(echo .)org \
--cc=samitolvanen@google$(echo .)com \
--cc=tony@atomide$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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