Searched refs:advisory (Results 1 – 25 of 77) sorted by relevance
1234
/external/tensorflow/tensorflow/security/ |
D | README.md | 16 | [TFSA-2022-084](https://github.com/tensorflow/tensorflow/blob/master/tensorflow/security/advisory… 17 | [TFSA-2022-083](https://github.com/tensorflow/tensorflow/blob/master/tensorflow/security/advisory… 18 | [TFSA-2022-082](https://github.com/tensorflow/tensorflow/blob/master/tensorflow/security/advisory… 19 | [TFSA-2022-081](https://github.com/tensorflow/tensorflow/blob/master/tensorflow/security/advisory… 20 | [TFSA-2022-080](https://github.com/tensorflow/tensorflow/blob/master/tensorflow/security/advisory… 21 | [TFSA-2022-079](https://github.com/tensorflow/tensorflow/blob/master/tensorflow/security/advisory… 22 | [TFSA-2022-078](https://github.com/tensorflow/tensorflow/blob/master/tensorflow/security/advisory… 23 | [TFSA-2022-077](https://github.com/tensorflow/tensorflow/blob/master/tensorflow/security/advisory… 24 | [TFSA-2022-076](https://github.com/tensorflow/tensorflow/blob/master/tensorflow/security/advisory… 25 | [TFSA-2022-075](https://github.com/tensorflow/tensorflow/blob/master/tensorflow/security/advisory… [all …]
|
/external/arm-trusted-firmware/docs/security_advisories/ |
D | index.rst | 9 security-advisory-tfv-1.rst 10 security-advisory-tfv-2.rst 11 security-advisory-tfv-3.rst 12 security-advisory-tfv-4.rst 13 security-advisory-tfv-5.rst 14 security-advisory-tfv-6.rst 15 security-advisory-tfv-7.rst 16 security-advisory-tfv-8.rst
|
D | security-advisory-tfv-6.rst | 27 This security advisory describes the current understanding of the Trusted 47 For Cortex-A57 and Cortex-A72 CPUs, the Pull Requests (PRs) in this advisory 51 For Cortex-A73 and Cortex-A75 CPUs, the PRs in this advisory invalidate the 60 on the PRs in this advisory being deployed in order for those workarounds to 89 | ``PSCI_VERSION`` baseline (without PRs in this advisory) | 515 | 91 | ``PSCI_VERSION`` baseline (with PRs in this advisory) | 527 |
|
/external/ruy/ruy/ |
D | ctx.cc | 51 void Ctx::set_performance_advisory(PerformanceAdvisory advisory) { in set_performance_advisory() argument 53 mutable_impl()->performance_advisory_ | advisory; in set_performance_advisory() 55 bool Ctx::performance_advisory(PerformanceAdvisory advisory) const { in performance_advisory() 56 return (impl().performance_advisory_ & advisory) != in performance_advisory()
|
D | ctx.h | 54 void set_performance_advisory(PerformanceAdvisory advisory); 55 bool performance_advisory(PerformanceAdvisory advisory) const;
|
D | context.cc | 50 bool Context::performance_advisory(PerformanceAdvisory advisory) const { in performance_advisory() 51 return ctx().performance_advisory(advisory); in performance_advisory()
|
D | context.h | 76 bool performance_advisory(PerformanceAdvisory advisory) const;
|
/external/llvm/docs/ |
D | ReportingGuide.rst | 13 confidential.** This isn't a public list and only `members`_ of the advisory 59 You will receive an email from the advisory committee acknowledging receipt 62 The advisory committee will immediately meet to review the incident and try to 79 Once the advisory committee has a complete account of the events they will make 102 After any incident, the advisory committee will make a report on the situation 120 advisory board itself, or the appropriateness of responses in general, but 129 The members serving on the advisory committee are listed here with contact 135 …FIXME: When we form the initial advisory committee, the members names and private contact info nee…
|
/external/rust/crates/userfaultfd/ |
D | SECURITY.md | 7 …issues via release notes as well as the [RustSec advisory database](https://github.com/RustSec/adv…
|
/external/rust/beto-rust/nearby/presence/ldt_np_adv_ffi/ |
D | deny.toml | 34 # The path where the advisory database is cloned/fetched into 35 db-path = "~/.cargo/advisory-db" 36 # The url(s) of the advisory databases to use 37 db-urls = ["https://github.com/rustsec/advisory-db"] 46 # https://github.com/rustsec/advisory-db 48 # A list of advisory IDs to ignore. Note that ignored advisories will still 63 # If this is true, then cargo deny will use the git executable to fetch advisory database.
|
/external/rust/beto-rust/nearby/ |
D | deny.toml | 34 # The path where the advisory database is cloned/fetched into 35 db-path = "~/.cargo/advisory-db" 36 # The url(s) of the advisory databases to use 37 db-urls = ["https://github.com/rustsec/advisory-db"] 46 # https://github.com/rustsec/advisory-db 48 # A list of advisory IDs to ignore. Note that ignored advisories will still 64 # If this is true, then cargo deny will use the git executable to fetch advisory database.
|
/external/cronet/third_party/boringssl/src/rust/bssl-crypto/ |
D | deny.toml | 34 # The path where the advisory database is cloned/fetched into 35 db-path = "~/.cargo/advisory-db" 36 # The url(s) of the advisory databases to use 37 db-urls = ["https://github.com/rustsec/advisory-db"] 46 # https://github.com/rustsec/advisory-db 48 # A list of advisory IDs to ignore. Note that ignored advisories will still 63 # If this is true, then cargo deny will use the git executable to fetch advisory database.
|
/external/boringssl/src/rust/bssl-crypto/ |
D | deny.toml | 34 # The path where the advisory database is cloned/fetched into 35 db-path = "~/.cargo/advisory-db" 36 # The url(s) of the advisory databases to use 37 db-urls = ["https://github.com/rustsec/advisory-db"] 46 # https://github.com/rustsec/advisory-db 48 # A list of advisory IDs to ignore. Note that ignored advisories will still 63 # If this is true, then cargo deny will use the git executable to fetch advisory database.
|
/external/curl/docs/ |
D | SECURITY-PROCESS.md | 55 - Write a security advisory draft about the problem that explains what the 63 - Update the "security advisory" with the CVE number. 78 announcement - attach the advisory draft for information with CVE and 114 1. Write up the security advisory, using markdown syntax. Use the same 117 2. Name the advisory file after the allocated CVE id. 121 4. Put the new advisory markdown file in the `curl-www/docs/` directory. Add it 126 6. On security advisory release day, push the changes on the curl-www
|
/external/deqp-deps/glslang/ |
D | SECURITY.md | 3 To report a security issue, please disclose it at [security advisory](https://github.com/KhronosGro…
|
/external/angle/third_party/vulkan-deps/glslang/src/ |
D | SECURITY.md | 3 To report a security issue, please disclose it at [security advisory](https://github.com/KhronosGro…
|
/external/rust/crates/grpcio-sys/grpc/third_party/cares/cares/ |
D | SECURITY.md | 58 - Write a security advisory draft about the problem that explains what the 66 vulnerability announcement - attach the advisory draft for information. Note 69 - Update the "security advisory" with the CVE number.
|
/external/arm-trusted-firmware/docs/process/ |
D | security.rst | 13 issues in the project's `issue tracker`_ with the ``security-advisory`` tag. You 40 with the source code and in any published security advisory.
|
/external/angle/third_party/vulkan-deps/spirv-tools/src/ |
D | SECURITY.md | 11 Please disclose it at [security advisory](https://github.com/KhronosGroup/SPIRV-Tools/security/advi…
|
/external/angle/third_party/vulkan-deps/spirv-headers/src/ |
D | SECURITY.md | 11 Please disclose it at [security advisory](https://github.com/KhronosGroup/SPIRV-Headers/security/ad…
|
/external/tensorflow/tensorflow/security/advisory/ |
D | tfsa-2019-002.md | 17 making the security advisory only to notify users that it is better to update to
|
D | tfsa-2022-015.md | 7 …ttps://github.com/tensorflow/tensorflow/blob/master/tensorflow/security/advisory/tfsa-2021-198.md)…
|
D | tfsa-2022-053.md | 16 …ttps://github.com/tensorflow/tensorflow/blob/master/tensorflow/security/advisory/tfsa-2021-198.md)…
|
D | tfsa-2022-085.md | 13 …ttps://github.com/tensorflow/tensorflow/blob/master/tensorflow/security/advisory/tfsa-2021-198.md)…
|
D | tfsa-2022-071.md | 19 …ttps://github.com/tensorflow/tensorflow/blob/master/tensorflow/security/advisory/tfsa-2021-198.md)…
|
1234