Home
last modified time | relevance | path

Searched refs:issues (Results 1 – 25 of 325) sorted by relevance

12345678910>>...13

/linux-5.19.10/Documentation/process/
Dembargoed-hardware-issues.rst3 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 …]
Dstable-kernel-rules.rst18 - Serious issues as reported by a user of a distribution kernel may also
25 - No "theoretical race condition" issues, unless an explanation of how the
154 members object to the patch, bringing up issues that the maintainers and
159 issues, some patches may be modified or dropped or additional patches may
161 issues are found.
Dstable-api-nonsense.rst45 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-5.19.10/drivers/gpu/drm/panfrost/
Dpanfrost_gpu.c166 u64 issues; member
169 u64 issues; member
178 .issues = hw_issues_##_name, \
185 .issues = hw_issues_##name##_r##_rev##p##_p##stat, \
285 hw_issues |= model->issues; in panfrost_gpu_init_features()
295 hw_issues |= model->revs[best].issues; in panfrost_gpu_init_features()
/linux-5.19.10/Documentation/vm/
Dzsmalloc.rst13 This was one of the major issues with its predecessor (xvmalloc).
15 To overcome these issues, zsmalloc allocates a bunch of 0-order pages
31 issues on 32-bit systems where the VA region for kernel space mappings
/linux-5.19.10/Documentation/admin-guide/
Dreporting-issues.rst4 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 …]
Dreporting-regressions.rst24 #. 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-5.19.10/Documentation/kbuild/
Dissues.rst2 Recursion issues
Dindex.rst20 issues
Dllvm.rst109 will build or work without any issues. Below is a general summary of
113 it or there are known issues. Using the latest stable version of LLVM or
160 - `Issue Tracker <https://github.com/ClangBuiltLinux/linux/issues>`_
164 - `Beginner Bugs <https://github.com/ClangBuiltLinux/linux/issues?q=is%3Aopen+is%3Aissue+label%3A%2…
/linux-5.19.10/Documentation/devicetree/bindings/power/reset/
Dkeystone-reset.txt38 WDT0 is triggered it issues hard reset for SoC.
59 WDT0 or WDT2 is triggered it issues soft reset for SoC.
/linux-5.19.10/Documentation/ABI/removed/
Dnet_dma7 coherency issues of the cpu potentially touching the buffers
Dvideo13948 performance issues in its first generation. Any video1394 user had
/linux-5.19.10/Documentation/translations/zh_CN/admin-guide/
Dsecurity-bugs.rst24 请查看“Documentation/translations/zh_CN/admin-guide/reporting-issues.rst”中
/linux-5.19.10/Documentation/translations/zh_TW/admin-guide/
Dsecurity-bugs.rst27 請查看「Documentation/translations/zh_TW/admin-guide/reporting-issues.rst」中
/linux-5.19.10/Documentation/userspace-api/media/dvb/
Dlegacy_dvb_apis.rst11 The DVBv3 frontend API has issues with new delivery systems, including
Dfrontend_legacy_api.rst24 kernel due to compatibility issues only. Their usage is strongly not
/linux-5.19.10/lib/vdso/
DKconfig19 This config option helps to avoid possible performance issues
/linux-5.19.10/drivers/gpu/drm/i915/
DKconfig.debug46 performance but will catch some internal issues.
139 performance but will catch some internal issues.
151 performance but will catch some internal issues.
163 performance but will help resolve GuC related issues.
/linux-5.19.10/Documentation/translations/zh_CN/process/
Dindex.rst48 embargoed-hardware-issues
/linux-5.19.10/drivers/staging/fwserial/
DTODO4 - I/O is handled asynchronously which presents some issues when error
/linux-5.19.10/Documentation/devicetree/bindings/csky/
Dpmu.txt6 it could count cpu's events for helping analysis performance issues.
/linux-5.19.10/Documentation/translations/zh_TW/process/
Dindex.rst51 embargoed-hardware-issues
/linux-5.19.10/Documentation/gpu/rfc/
Dindex.rst6 design issues before getting lost in the code details. This section is meant to
/linux-5.19.10/Documentation/devicetree/bindings/net/wireless/
Dsilabs,wfx.yaml27 it, you may encounter issues during reboot. The mmc-pwrseq should be
66 during probe. Without this property, you may encounter issues with warm

12345678910>>...13