From: Cornelia Huck <cohuck@redhat.com>
To: Shaoqin Huang <shahuang@redhat.com>,
qemu-devel@nongnu.org, qemu-arm@nongnu.org
Cc: oliver.upton@linux.dev, salil.mehta@huawei.com,
james.morse@arm.com, gshan@redhat.com,
Shaoqin Huang <shahuang@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH v1 2/5] linux-headers: Import arm-smccc.h from Linux v6.4-rc7
Date: Tue, 04 Jul 2023 11:05:35 +0200 [thread overview]
Message-ID: <87a5wchwrk.fsf@redhat.com> (raw)
In-Reply-To: <20230626064910.1787255-3-shahuang@redhat.com>
On Mon, Jun 26 2023, Shaoqin Huang <shahuang@redhat.com> wrote:
> Copy in the SMCCC definitions from the kernel, which will be used to
> implement SMCCC handling in userspace.
>
> Signed-off-by: Shaoqin Huang <shahuang@redhat.com>
> ---
> linux-headers/linux/arm-smccc.h | 240 ++++++++++++++++++++++++++++++++
> 1 file changed, 240 insertions(+)
> create mode 100644 linux-headers/linux/arm-smccc.h
I think you need to add this to the headers update script, so that
changes get propagated in the future as well.
(I'd just add it to the script and do the update in one go.)
next prev parent reply other threads:[~2023-07-04 9:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-26 6:49 [PATCH v1 0/5] target/arm: Handle psci calls in userspace Shaoqin Huang
2023-06-26 6:49 ` [PATCH v1 1/5] linux-headers: Update to v6.4-rc7 Shaoqin Huang
2023-06-26 6:49 ` [PATCH v1 2/5] linux-headers: Import arm-smccc.h from Linux v6.4-rc7 Shaoqin Huang
2023-07-04 9:05 ` Cornelia Huck [this message]
2023-06-26 6:49 ` [PATCH v1 3/5] target/arm: make psci call can be used by kvm Shaoqin Huang
2023-06-26 6:49 ` [PATCH v1 4/5] arm/kvm: add skeleton implementation for userspace SMCCC call handling Shaoqin Huang
2023-07-04 9:17 ` Cornelia Huck
2023-06-26 6:49 ` [PATCH v1 5/5] arm/kvm: add support for userspace psci calls handling Shaoqin Huang
2023-06-26 13:42 ` [PATCH v1 0/5] target/arm: Handle psci calls in userspace Salil Mehta via
2023-06-27 2:34 ` Shaoqin Huang
2023-07-04 9:58 ` Salil Mehta via
2023-07-13 0:27 ` Gavin Shan
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=87a5wchwrk.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=gshan@redhat.com \
--cc=james.morse@arm.com \
--cc=mst@redhat.com \
--cc=oliver.upton@linux.dev \
--cc=pbonzini@redhat.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=salil.mehta@huawei.com \
--cc=shahuang@redhat.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;
as well as URLs for NNTP newsgroup(s).