| /kernel/linux/linux-5.10/Documentation/kbuild/ |
| D | issues.rst | 5 issue #1
8 .. literalinclude:: Kconfig.recursion-issue-01
11 issue #2
14 .. literalinclude:: Kconfig.recursion-issue-02
|
| D | Kconfig.recursion-issue-01 | 1 # Simple Kconfig recursive issue
6 # make KBUILD_KCONFIG=Documentation/kbuild/Kconfig.recursion-issue-01 allnoconfig
8 # This Kconfig file has a simple recursive dependency issue. In order to
9 # understand why this recursive dependency issue occurs lets consider what
36 # Reading the Documentation/kbuild/Kconfig.recursion-issue-01 file it may be
41 # implications of this recursive issue where the solution is perhaps not so
45 mainmenu "Simple example to demo kconfig recursive dependency issue"
|
| D | Kconfig.recursion-issue-02 | 1 # Cumulative Kconfig recursive issue
6 # make KBUILD_KCONFIG=Documentation/kbuild/Kconfig.recursion-issue-02 allnoconfig
23 # The example provided in Documentation/kbuild/Kconfig.recursion-issue-02
30 # other bells in the system cannot negate. The reason for this issue is
41 # For an example real world scenario issue refer to the attempt to remove
|
| D | Kconfig.select-break | 1 # Select broken dependency issue
13 # example of this issue is below.
21 mainmenu "Simple example to demo kconfig select broken dependency issue"
|
| D | kconfig-language.rst | 560 into a recursive dependency issue with Kconfig, a recursive dependency can be
566 Kconfig recursive issue" subsection below. Kconfig does not do recursive
573 Simple Kconfig recursive issue
576 Read: Documentation/kbuild/Kconfig.recursion-issue-01
580 make KBUILD_KCONFIG=Documentation/kbuild/Kconfig.recursion-issue-01 allnoconfig
582 Cumulative Kconfig recursive issue
585 Read: Documentation/kbuild/Kconfig.recursion-issue-02
589 make KBUILD_KCONFIG=Documentation/kbuild/Kconfig.recursion-issue-02 allnoconfig
591 Practical solutions to kconfig recursive issue
594 Developers who run into the recursive Kconfig issue have two options
[all …]
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | blk_types.h | 180 static inline u64 bio_issue_time(struct bio_issue *issue) in bio_issue_time() argument
182 return __bio_issue_time(issue->value); in bio_issue_time()
185 static inline sector_t bio_issue_size(struct bio_issue *issue) in bio_issue_size() argument
187 return ((issue->value & BIO_ISSUE_SIZE_MASK) >> BIO_ISSUE_SIZE_SHIFT); in bio_issue_size()
190 static inline void bio_issue_init(struct bio_issue *issue, in bio_issue_init() argument
194 issue->value = ((issue->value & BIO_ISSUE_RES_MASK) | in bio_issue_init()
|
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| D | sysfs-bus-usb-lvstest | 9 Write to this node to issue "Get Device Descriptor"
32 Write to this node to issue "Reset" for Link Layer Validation
39 Write to this node to issue "U3 entry" for Link Layer
46 Write to this node to issue "U3 exit" for Link Layer
58 Write to this node to issue "Warm Reset" for Link Layer Validation
|
| /kernel/linux/linux-5.10/ |
| D | README | 26 Using scripts/checkpatch.pl to make sure there's no coding style issue.
137 If the patch is related to CVE or issue/bugzilla, then we need add the
141 issue: $issue-id or NA
144 issue: https://gitee.com/openharmony/kernel_linux/issues
160 issue: $issue-id [O]
181 issue: $issue-id [O]
199 issue: $issue-id or NA [O]
215 issue: 1000
|
| /kernel/linux/linux-5.10/samples/bpf/ |
| D | xdp_rxq_info_kern.c | 37 __u64 issue; member
102 rec->issue++; in xdp_prognum0()
117 rxq_rec->issue++; in xdp_prognum0()
|
| D | xdp_redirect_cpu_kern.c | 32 __u64 issue; member
226 rec->issue++; in xdp_prognum0_no_touch()
269 rec->issue++; in xdp_prognum1_touch_data()
317 rec->issue++; in xdp_prognum2_round_robin()
385 rec->issue++; in xdp_prognum3_proto_separate()
461 rec->issue++; in xdp_prognum4_ddos_filter_pktgen()
564 rec->issue++; in xdp_prognum5_lb_hash_ip_pairs()
684 rec->issue += 1; in trace_xdp_cpumap_enqueue()
727 rec->issue++; in trace_xdp_cpumap_kthread()
|
| D | xdp_rxq_info_user.c | 185 __u64 issue; member
276 rec->cpu[i].issue = values[i].issue; in map_collect_percpu()
277 sum_issue += values[i].issue; in map_collect_percpu()
280 rec->total.issue = sum_issue; in map_collect_percpu()
328 packets = r->issue - p->issue; in calc_errs_pps()
|
| D | xdp_redirect_cpu_user.c | 180 __u64 issue; member
225 rec->cpu[i].issue = values[i].issue; in map_collect_percpu()
226 sum_issue += values[i].issue; in map_collect_percpu()
236 rec->total.issue = sum_issue; in map_collect_percpu()
334 packets = r->issue - p->issue; in calc_errs_pps()
|
| /kernel/linux/linux-5.10/Documentation/networking/device_drivers/ethernet/intel/ |
| D | ice.rst | 44 If an issue is identified with the released source code on a supported kernel
45 with a supported adapter, email the specific information related to the issue
|
| D | igbvf.rst | 63 If an issue is identified with the released source code on a supported kernel
64 with a supported adapter, email the specific information related to the issue
|
| D | ixgbevf.rst | 65 If an issue is identified with the released source code on a supported kernel
66 with a supported adapter, email the specific information related to the issue
|
| /kernel/linux/linux-5.10/drivers/gpu/drm/panfrost/ |
| D | panfrost_issues.h | 252 enum panfrost_hw_issue issue) in panfrost_has_hw_issue() argument
254 return test_bit(issue, pfdev->features.hw_issues); in panfrost_has_hw_issue()
|
| D | TODO | 6 - Bifrost specific feature and issue handling
|
| /kernel/uniproton/doc/ |
| D | contribute_guide.md | 480 如果当前 commit 针对某个issue，那么可以在 Footer 部分关闭这个 issue 。
636 >- 如果提交的代码是为了解决issue问题，记得将issue和此次代码提交相关联，关联方法请参考<a href="https://gitee.com/help/articles/4141" t…
761 …欢迎<a href="https://gitee.com/openeuler/UniProton/issues" target="_blank">提交issue</a>对关心的问题发起讨论，欢迎到…
|
| /kernel/linux/linux-5.10/Documentation/process/ |
| D | embargoed-hardware-issues.rst | 36 issue according to our documented process.
99 will form the initial response team for a particular issue. The initial
101 the issue in the best technical way.
105 immediate exclusion from the current issue and removal from all related
139 issue after confirming with the developers that they will adhere to this
142 issue after initial contact. The hardware security team is supporting the
152 entities who have already been, or should be, informed about the issue.
161 - If an expert which is required to handle an issue is employed by an
243 disclosure of a particular issue, unless requested by a response team or by
|
| /kernel/linux/linux-5.10/Documentation/driver-api/soundwire/ |
| D | error_handling.rst | 25 indication of a bus allocation issue. The interrupt mechanism can also help
35 Slave or to a non-implemented register) or electrical issue, no response
39 solution. Alternatively some implementations might directly issue a bus
|
| /kernel/linux/linux-5.10/arch/alpha/lib/ |
| D | strlen.S | 35 nop # helps dual issue last two insns
|
| /kernel/linux/linux-5.10/block/ |
| D | blk-rq-qos.c | 53 if (rqos->ops->issue) in __rq_qos_issue()
54 rqos->ops->issue(rqos, rq); in __rq_qos_issue()
|
| D | blk-wbt.c | 219 u64 now, issue = READ_ONCE(rwb->sync_issue); in rwb_sync_issue_lat() local
221 if (!issue || !rwb->sync_cookie) in rwb_sync_issue_lat()
225 return now - issue; in rwb_sync_issue_lat()
805 .issue = wbt_issue,
|
| /kernel/linux/linux-5.10/arch/arm64/boot/dts/qcom/ |
| D | sdm630-sony-xperia-ganges.dtsi | 26 * issue with it that has to be resolved.
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/serial/ |
| D | nvidia,tegra20-hsuart.txt | 39 Tegra186 chip has a known hardware issue. UART Rx baud rate tolerance level
53 to the issue stated above, baud rate on Tegra UART should be set equal to or
|