From: Tom Rini <trini@konsulko.com>
To: Johannes Krottmayer <johannes@krotti42.com>
Cc: u-boot@lists.denx.de
Subject: Re: [PATCH 1/1] arm: cpu: armv7m: add required .type name, %function directive
Date: Wed, 7 May 2025 16:51:23 -0600 [thread overview]
Message-ID: <20250507225123.GR5430@bill-the-cat> (raw)
In-Reply-To: <a138ecb5-680e-4272-8211-dbb354745247@krotti42.com>
[-- Attachment #1: Type: text/plain, Size: 608 bytes --]
On Wed, May 07, 2025 at 07:07:03PM +0000, Johannes Krottmayer wrote:
> Hi Tom!
>
> Okay, STT_FUNC is an alternative spelling for %function, didn't
> know that before. So my question is deprecated.
>
> Sorry, for wasting your time.
>
> BTW, I will add the required macros and also try to add the VFP
> support. But I think it's better in two different patches. First
> patch with the ENTRY/ENDPROC macros and later with the VFP patch.
Ah, thanks. I too didn't know about STT_FUNC until now. So I think that
means all we really need then is to use ENTRY/ENDPROC on that function?
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2025-05-07 22:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-07 6:07 [PATCH 0/1] arm: add required assembler directive (binutils >=2.44) Johannes Krottmayer
2025-05-07 6:07 ` [PATCH 1/1] arm: cpu: armv7m: add required .type name, %function directive Johannes Krottmayer
2025-05-07 16:55 ` Tom Rini
2025-05-07 18:17 ` Johannes Krottmayer
2025-05-07 19:07 ` Johannes Krottmayer
2025-05-07 21:18 ` Johannes Krottmayer
2025-05-07 22:51 ` Tom Rini [this message]
2025-05-07 23:36 ` Johannes Krottmayer
2025-05-08 19:00 ` [PATCH v2 1/1] arm: cpu: armv7m: add ENTRY/ENDPROC macros Johannes Krottmayer
2025-05-08 19:09 ` Johannes Krottmayer
2025-05-08 19:34 ` Tom Rini
2025-05-08 19:33 ` Tom Rini
2025-05-22 19:36 ` Tom Rini
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=20250507225123.GR5430@bill-the-cat \
--to=trini@konsulko.com \
--cc=johannes@krotti42.com \
--cc=u-boot@lists.denx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.