Searched refs:scope (Results 1 – 20 of 20) sorted by relevance
/trusted-firmware-a-latest/ |
D | .commitlintrc.js | 40 const scope = subsection.scope ? [ subsection.scope ] : []; 43 return scope.concat(subscopes);
|
D | .versionrc.js | 49 const scope = subsection.scope ? [ subsection.scope ] : []; 54 "scopes": scope.concat(subsection.deprecated || []),
|
/trusted-firmware-a-latest/tools/conventional-changelog-tf-a/templates/ |
D | commit.hbs | 1 {{#if scope }} 2 {{~#if showScope }}**{{ scope }}:** {{/if}}
|
/trusted-firmware-a-latest/tools/conventional-changelog-tf-a/ |
D | index.js | 76 notes: notes.filter(note => section.scopes?.includes(note.commit.scope)), 95 … !flattenedSections.some(section => section.scopes?.includes(note.commit.scope))), 110 commits: commits.filter(commit => section.scopes?.includes(commit.scope)), 129 !flattenedSections.some(section => section.scopes?.includes(commit.scope))), 176 if ((commit.type === "build") && (commit.scope == null)) { 177 commit.scope = "build";
|
/trusted-firmware-a-latest/tools/sptool/ |
D | spactions.py | 98 scope = "global" 99 args = action(sp_layout, scope, args) 100 args = append_called(action, scope, args)
|
/trusted-firmware-a-latest/docs/process/ |
D | commit-style.rst | 4 When writing commit messages, please think carefully about the purpose and scope 33 <type>[optional scope]: <description> 40 ``refactor`` type and the ``amu`` scope: 84 has a single scope that is considered to be blessed, and possibly several 101 does not yet have a designated scope, please add one. 113 scope: foo 117 scope: bar
|
/trusted-firmware-a-latest/drivers/console/ |
D | multi_console.c | 68 void console_set_scope(console_t *console, unsigned int scope) in console_set_scope() argument 72 console->flags = (console->flags & ~CONSOLE_FLAG_SCOPE_MASK) | scope; in console_set_scope()
|
/trusted-firmware-a-latest/include/drivers/ |
D | console.h | 80 void console_set_scope(console_t *console, unsigned int scope);
|
/trusted-firmware-a-latest/docs/threat_model/ |
D | threat_model_rss_interface.rst | 14 The scope of this threat model only includes the interface between the RSS and
|
D | threat_model_fvp_r.rst | 28 out-of-scope for this threat-model.
|
D | threat_model.rst | 19 shown on Figure 1. Everything else on Figure 1 is outside of the scope of 136 in scope of this threat model. 162 considered out-of-scope. 165 chip, notably those like Power Analysis Attacks, are out-of-scope. Power
|
D | threat_model_el3_spm.rst | 19 The scope for this threat model is:
|
/trusted-firmware-a-latest/docs/components/fconf/ |
D | index.rst | 132 within the platform API and are defined only inside the platform scope. The
|
/trusted-firmware-a-latest/docs/design/ |
D | trusted-board-boot-build.rst | 113 NS_BL2U and SCP_BL2U) is outside the scope of this document.
|
/trusted-firmware-a-latest/docs/security_advisories/ |
D | security-advisory-tfv-6.rst | 119 scope of TF. However, an example implementation in the minimal AArch32 Secure
|
/trusted-firmware-a-latest/docs/design_documents/ |
D | cmake_framework.rst | 41 * Language is problematic (e.g. variable scope).
|
D | measured_boot_poc.rst | 70 service as provided by TF-A. As such, it is beyond the scope of this
|
/trusted-firmware-a-latest/docs/components/ |
D | firmware-update.rst | 38 The design of the ``Client`` and ``Update Agent`` is out of scope of this 119 This document describes the secure world FWU design. It is beyond its scope to
|
/trusted-firmware-a-latest/docs/ |
D | porting-guide.rst | 3228 use in the crash scope that are able to support this, i.e. that are written
|
D | change-log.md | 55 - **threat_model:** mark power analysis threats out-of-scope ([11cb096](https://review.trustedfirmw… 4276 …- change scope-case to lower-case ([804e52e](https://review.trustedfirmware.org/plugins/gitiles/TF… 8854 implementation has been cleaned up and reduced in scope.
|