From: abdellatif.elkhlifi@arm.com
To: meta-arm@lists.yoctoproject.org, Jon.Mason@arm.com
Cc: Abdellatif El Khlifi <abdellatif.elkhlifi@arm.com>
Subject: [PATCH] arm-bsp/corstone1000: add documentation disclaimer
Date: Tue, 2 Apr 2024 15:18:46 +0100 [thread overview]
Message-ID: <20240402141846.48855-1-abdellatif.elkhlifi@arm.com> (raw)
From: Abdellatif El Khlifi <abdellatif.elkhlifi@arm.com>
add Security Vulnerability Disclaimer in Corstone-1000 documentation
Signed-off-by: Abdellatif El Khlifi <abdellatif.elkhlifi@arm.com>
---
.../documentation/corstone1000/index.rst | 18 ++++++++++++++----
1 file changed, 14 insertions(+), 4 deletions(-)
diff --git a/meta-arm-bsp/documentation/corstone1000/index.rst b/meta-arm-bsp/documentation/corstone1000/index.rst
index 8626c42c..cbe78c5d 100644
--- a/meta-arm-bsp/documentation/corstone1000/index.rst
+++ b/meta-arm-bsp/documentation/corstone1000/index.rst
@@ -1,11 +1,21 @@
..
- # Copyright (c) 2022, Arm Limited.
+ # Copyright (c) 2022, 2024, Arm Limited.
#
# SPDX-License-Identifier: MIT
-################
-ARM Corstone1000
-################
+#################
+Arm Corstone-1000
+#################
+
+*************************
+Disclaimer
+*************************
+
+Arm reference solutions are Arm public example software projects that track and
+pull upstream components, incorporating their respective security fixes
+published over time. Arm partners are responsible for ensuring that the
+components they use contain all the required security fixes, if and when they
+deploy a product derived from Arm reference solutions.
.. toctree::
:maxdepth: 1
--
2.25.1
next reply other threads:[~2024-04-02 14:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-02 14:18 abdellatif.elkhlifi [this message]
2024-04-03 13:19 ` [PATCH] arm-bsp/corstone1000: add documentation disclaimer Jon Mason
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=20240402141846.48855-1-abdellatif.elkhlifi@arm.com \
--to=abdellatif.elkhlifi@arm.com \
--cc=Jon.Mason@arm.com \
--cc=meta-arm@lists.yoctoproject.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).