Searched refs:issues (Results 1 – 25 of 289) sorted by relevance
12345678910>>...12
| /kernel/liteos_a/ |
| D | CHANGELOG.md | 8 …89b0f95a65354d7d86)), closes [#I4I0O8](https://gitee.com/openharmony/kernel_liteos_a/issues/I4I0O8)
9 …6a543c029cc6dd75be)), closes [#I4NY49](https://gitee.com/openharmony/kernel_liteos_a/issues/I4NY49)
10 …45c0534db88b9c666f)), closes [#I4CLL9](https://gitee.com/openharmony/kernel_liteos_a/issues/I4CLL9)
11 …124b538e423023a259)), closes [#I4ATQX](https://gitee.com/openharmony/kernel_liteos_a/issues/I4ATQX)
12 …48a50a253bc2a3b604)), closes [#I4BL3S](https://gitee.com/openharmony/kernel_liteos_a/issues/I4BL3S)
13 …aa041ab4da8570c6a1)), closes [#I452Z7](https://gitee.com/openharmony/kernel_liteos_a/issues/I452Z7)
17 …690403ac652bbcea72)), closes [#I4NOC7](https://gitee.com/openharmony/kernel_liteos_a/issues/I4NOC7)
18 …65ebfe494d491fe20f)), closes [#I4KEZ1](https://gitee.com/openharmony/kernel_liteos_a/issues/I4KEZ1)
19 …a2b48fe0ac6dd19ff2)), closes [#I4CYPZ](https://gitee.com/openharmony/kernel_liteos_a/issues/I4CYPZ)
20 …56f575e3abc6c10702)), closes [#I2WARC](https://gitee.com/openharmony/kernel_liteos_a/issues/I2WARC)
[all …]
|
| /kernel/liteos_m/ |
| D | CHANGELOG.md | 6 …5a099e90f62c86abd1)), closes [#I4D129](https://gitee.com/openharmony/kernel_liteos_m/issues/I4D129)
7 …01873fe8e8d8cdd3c6)), closes [#I4K7LL](https://gitee.com/openharmony/kernel_liteos_m/issues/I4K7LL)
8 …768198eccc7448df6c)), closes [#I4SQIQ](https://gitee.com/openharmony/kernel_liteos_m/issues/I4SQIQ)
9 …eab976bdc1b32d1db9)), closes [#I4D1HY](https://gitee.com/openharmony/kernel_liteos_m/issues/I4D1HY)
12 …0fc9ca9e392537419f)), closes [#I4DAOU](https://gitee.com/openharmony/kernel_liteos_m/issues/I4DAOU)
13 …3b1b5aeca2d097289b)), closes [#I4ENQ1](https://gitee.com/openharmony/kernel_liteos_m/issues/I4ENQ1)
15 …185382e3228ed4b0a7)), closes [#I4N9P8](https://gitee.com/openharmony/kernel_liteos_m/issues/I4N9P8)
16 …3cf74645f470edf9b5)), closes [#I4O204](https://gitee.com/openharmony/kernel_liteos_m/issues/I4O204)
17 …46a73a7fb291588eda)), closes [#I4EJI4](https://gitee.com/openharmony/kernel_liteos_m/issues/I4EJI4)
18 …3f7a4280460bbf353a)), closes [#I4SJPZ](https://gitee.com/openharmony/kernel_liteos_m/issues/I4SJPZ)
[all …]
|
| /kernel/linux/build/ |
| D | kernel_build.py | 80 issues = {}
101 if filename in issues:
102 issues[filename].extend(details)
104 issues[filename] = details
111 if filename in issues:
112 issues[filename].extend(details)
114 issues[filename] = details
116 for filename, details in issues.items():
|
| /kernel/linux/linux-5.10/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 | 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
|
| /kernel/linux/linux-5.10/drivers/gpu/drm/panfrost/ |
| D | panfrost_gpu.c | 163 u64 issues; member
166 u64 issues; member
175 .issues = hw_issues_##_name, \
182 .issues = hw_issues_##name##_r##_rev##p##_p##stat, \
281 hw_issues |= model->issues; in panfrost_gpu_init_features()
291 hw_issues |= model->revs[best].issues; in panfrost_gpu_init_features()
|
| /kernel/linux/linux-5.10/Documentation/vm/ |
| D | zsmalloc.rst | 13 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
|
| /kernel/linux/linux-5.10/Documentation/kbuild/ |
| D | issues.rst | 2 Recursion issues
|
| D | index.rst | 20 issues
|
| D | llvm.rst | 71 - `Issue Tracker <https://github.com/ClangBuiltLinux/linux/issues>`_
75 - `Beginner Bugs <https://github.com/ClangBuiltLinux/linux/issues?q=is%3Aopen+is%3Aissue+label%3A%2…
|
| /kernel/linux/linux-5.10/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.
|
| /kernel/linux/linux-5.10/Documentation/ABI/removed/ |
| D | net_dma | 7 coherency issues of the cpu potentially touching the buffers
|
| D | video1394 | 8 performance issues in its first generation. Any video1394 user had
|
| /kernel/linux/linux-5.10/drivers/staging/media/atomisp/ |
| D | TODO | 5 V4L2 driver, there are still some issues preventing it to
8 Solving the related bugs and issues preventing it to work is
40 5. There are several issues related to memory management, causing
66 6. There is some issues at the frame receive logic, causing the
|
| /kernel/linux/linux-5.10/drivers/gpu/drm/i915/ |
| D | Kconfig.debug | 41 performance but will catch some internal issues.
119 performance but will catch some internal issues.
131 performance but will catch some internal issues.
143 performance but will help resolve GuC related issues.
|
| /kernel/linux/linux-5.10/lib/vdso/ |
| D | Kconfig | 19 This config option helps to avoid possible performance issues
|
| /kernel/linux/linux-5.10/Documentation/translations/zh_CN/process/ |
| D | index.rst | 48 embargoed-hardware-issues
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/dvb/ |
| D | frontend_legacy_api.rst | 24 kernel due to compatibility issues only. Their usage is strongly not
|
| D | legacy_dvb_apis.rst | 11 The DVBv3 frontend API has issues with new delivery systems, including
|
| /kernel/linux/linux-5.10/drivers/staging/fwserial/ |
| D | TODO | 4 - I/O is handled asynchronously which presents some issues when error
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/csky/ |
| D | pmu.txt | 6 it could count cpu's events for helping analysis performance issues.
|
| /kernel/linux/linux-5.10/Documentation/power/ |
| D | tricks.rst | 25 * due to video issues, swsusp should be easier to get working than
|
| /kernel/linux/linux-5.10/Documentation/scsi/ |
| D | tcm_qla2xxx.rst | 23 and other fabric issues.
|
| /kernel/linux/linux-5.10/Documentation/driver-api/firmware/ |
| D | lookup-order.rst | 7 a driver issues a firmware API call.
|
| /kernel/linux/linux-5.10/Documentation/usb/ |
| D | ehci.rst | 51 used on PPC hardware so big/little endianness issues should be gone.
53 systems with interesting DMA mapping issues.
84 There are some issues with power management; suspend/resume doesn't
156 but aggregate throughput is also affected by issues like delays between
224 Interrupt and ISO transfer performance issues. Those periodic
|
12345678910>>...12