From: Ross Burton <Ross.Burton@arm.com>
To: Steve Sakoman <steve@sakoman.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>,
"vkumbhar@mvista.com" <vkumbhar@mvista.com>
Subject: Re: [OE-core] [PATCH][kirkstone] openssl: fix crash on aarch64 if BTI is enabled but no Crypto instructions
Date: Tue, 16 Apr 2024 12:42:32 +0000 [thread overview]
Message-ID: <A328C99D-E275-45C4-A911-D86FC48AE45A@arm.com> (raw)
In-Reply-To: <CAOSpxdbCRMVfXhf7jOVYA5rgu1nayGW03NiDk5yWj_kJBU24jA@mail.gmail.com>
On 29 Mar 2024, at 13:31, Steve Sakoman <steve@sakoman.com> wrote:
>
> Sorry for the delayed response, but I found the same issue with the
> kirkstone version that Vivek did.
Sorry for the very delayed response, I somehow missed this reply in my inbox.
The patched code doesn’t exist in kirkstone so this isn’t needed, I thought I tested this patch before posting but maybe I did something stupid.
Sorry for the inconvenience,
Ross
prev parent reply other threads:[~2024-04-16 12:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-27 11:15 [PATCH][kirkstone] openssl: fix crash on aarch64 if BTI is enabled but no Crypto instructions ross.burton
2024-03-29 3:51 ` Vivek Kumbhar
2024-03-29 13:31 ` [OE-core] " Steve Sakoman
2024-04-16 12:42 ` Ross Burton [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=A328C99D-E275-45C4-A911-D86FC48AE45A@arm.com \
--to=ross.burton@arm.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=steve@sakoman.com \
--cc=vkumbhar@mvista.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