Searched refs:issues (Results 1 – 25 of 357) sorted by relevance
12345678910>>...15
/Linux-v6.6/Documentation/process/ |
D | embargoed-hardware-issues.rst | 3 Embargoed hardware issues 9 Hardware issues which result in security problems are a different category 13 Hardware issues like Meltdown, Spectre, L1TF etc. must be treated 16 hardware vendors and other parties. For some of the issues, software 29 issues. Reports of pure software security bugs in the Linux kernel are not 46 While hardware security issues are often handled by the affected hardware 79 is aware of the sensitive nature of such issues and offers a Memorandum of 87 keep hardware security issues under embargo for coordination between 91 issues in the past and has the necessary mechanisms in place to allow 95 initial contact, which oversees the process of handling such issues under [all …]
|
D | maintainer-soc-clean-dts.rst | 19 results of issues in an included DTSI file, are considered existing, not new 24 issues shall be fixed in reasonable time (e.g. within one release) or the
|
D | index.rst | 38 For security issues, see: 44 embargoed-hardware-issues
|
D | stable-api-nonsense.rst | 45 First off, I'm not going to address **any** legal issues about closed 50 the technical issues here (not to make light of the legal issues, they 84 Now a number of these issues can be addressed by simply compiling your 120 issues: 146 Security issues are also very important for Linux. When a
|
/Linux-v6.6/drivers/gpu/drm/panfrost/ |
D | panfrost_gpu.c | 157 u64 issues; member 160 u64 issues; member 169 .issues = hw_issues_##_name, \ 176 .issues = hw_issues_##name##_r##_rev##p##_p##stat, \ 287 hw_issues |= model->issues; in panfrost_gpu_init_features() 297 hw_issues |= model->revs[best].issues; in panfrost_gpu_init_features()
|
/Linux-v6.6/Documentation/translations/zh_CN/admin-guide/ |
D | reporting-regressions.rst | 31 #. 按照 Documentation/translations/zh_CN/admin-guide/reporting-issues.rst 中 74 只需按照 Documentation/translations/zh_CN/admin-guide/reporting-issues.rst 中 136 如 Documentation/translations/zh_CN/admin-guide/reporting-issues.rst (简要)
|
D | security-bugs.rst | 24 请查看“Documentation/translations/zh_CN/admin-guide/reporting-issues.rst”中
|
/Linux-v6.6/Documentation/admin-guide/ |
D | reporting-issues.rst | 4 Reporting issues 40 If you are facing multiple issues with the Linux kernel at once, report each 51 Step-by-step guide how to report issues to the kernel maintainers 54 The above TL;DR outlines roughly how to report issues to the Linux kernel 56 reporting issues to Free/Libre & Open Source Software (FLOSS) projects. For 72 will often be needed anyway to hunt down and fix issues. 80 issue, or a really severe problem: those are 'issues of high priority' that 96 issues at once, create separate notes for each of them and make sure they 107 time this won't be bugzilla.kernel.org, as issues typically need to be sent 129 up there, scroll down to the instructions for issues only happening with [all …]
|
D | reporting-regressions.rst | 24 #. Report your issue as outlined in Documentation/admin-guide/reporting-issues.rst, 57 behavior with a newer kernel version; such issues can be caused by changes in 77 Documentation/admin-guide/reporting-issues.rst, it already describes the 146 a lot of issues only occur in a particular environment outside the developer's 158 Documentation/admin-guide/reporting-issues.rst and described in more detail by 184 issues, or other problematic aspects already fixed in later versions 254 In extremely rare situations security issues can't be fixed without causing 258 issues without causing regressions. 389 What kind of issues are supposed to be tracked by regzbot? 393 regular issues. But it's okay for the Linux kernel's regression tracker if you [all …]
|
/Linux-v6.6/Documentation/kbuild/ |
D | issues.rst | 2 Recursion issues
|
D | index.rst | 20 issues
|
D | llvm.rst | 141 will build or work without any issues. Below is a general summary of 145 it or there are known issues. Using the latest stable version of LLVM or 195 - `Issue Tracker <https://github.com/ClangBuiltLinux/linux/issues>`_ 199 - `Beginner Bugs <https://github.com/ClangBuiltLinux/linux/issues?q=is%3Aopen+is%3Aissue+label%3A%2…
|
/Linux-v6.6/drivers/gpu/drm/amd/display/ |
D | Kconfig | 10 # !CC_IS_CLANG: https://github.com/ClangBuiltLinux/linux/issues/1752 21 has been resolved: https://github.com/llvm/llvm-project/issues/41896.
|
/Linux-v6.6/drivers/gpu/drm/ci/xfails/ |
D | i915-apl-skips.txt | 5 # This is cascading issues
|
/Linux-v6.6/Documentation/devicetree/bindings/power/reset/ |
D | keystone-reset.txt | 38 WDT0 is triggered it issues hard reset for SoC. 59 WDT0 or WDT2 is triggered it issues soft reset for SoC.
|
/Linux-v6.6/Documentation/ABI/removed/ |
D | net_dma | 7 coherency issues of the cpu potentially touching the buffers
|
/Linux-v6.6/Documentation/translations/zh_TW/admin-guide/ |
D | security-bugs.rst | 27 請查看「Documentation/translations/zh_TW/admin-guide/reporting-issues.rst」中
|
/Linux-v6.6/drivers/gpu/drm/i915/ |
D | Kconfig.debug | 46 performance but will catch some internal issues. 139 performance but will catch some internal issues. 151 performance but will catch some internal issues. 164 performance but will help resolve GuC related issues.
|
/Linux-v6.6/Documentation/userspace-api/media/dvb/ |
D | legacy_dvb_apis.rst | 11 The DVBv3 frontend API has issues with new delivery systems, including
|
D | frontend_legacy_api.rst | 24 kernel due to compatibility issues only. Their usage is strongly not
|
/Linux-v6.6/lib/vdso/ |
D | Kconfig | 19 This config option helps to avoid possible performance issues
|
/Linux-v6.6/Documentation/translations/zh_CN/process/ |
D | index.rst | 48 embargoed-hardware-issues
|
/Linux-v6.6/Documentation/translations/zh_TW/process/ |
D | index.rst | 50 embargoed-hardware-issues
|
/Linux-v6.6/arch/arm64/boot/dts/freescale/ |
D | imx8qm-apalis.dtsi | 328 * issues with certain SD cards, disable 1.8V signaling for now. 337 * issues with certain SD cards, disable 1.8V signaling for now.
|
/Linux-v6.6/Documentation/devicetree/bindings/csky/ |
D | pmu.txt | 6 it could count cpu's events for helping analysis performance issues.
|
12345678910>>...15