| /Linux-v5.4/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 | 542 into a recursive dependency issue with Kconfig, a recursive dependency can be
548 Kconfig recursive issue" subsection below. Kconfig does not do recursive
555 Simple Kconfig recursive issue
558 Read: Documentation/kbuild/Kconfig.recursion-issue-01
562 make KBUILD_KCONFIG=Documentation/kbuild/Kconfig.recursion-issue-01 allnoconfig
564 Cumulative Kconfig recursive issue
567 Read: Documentation/kbuild/Kconfig.recursion-issue-02
571 make KBUILD_KCONFIG=Documentation/kbuild/Kconfig.recursion-issue-02 allnoconfig
573 Practical solutions to kconfig recursive issue
576 Developers who run into the recursive Kconfig issue have two options
[all …]
|
| /Linux-v5.4/include/linux/ |
| D | blk_types.h | 121 static inline u64 bio_issue_time(struct bio_issue *issue) in bio_issue_time() argument
123 return __bio_issue_time(issue->value); in bio_issue_time()
126 static inline sector_t bio_issue_size(struct bio_issue *issue) in bio_issue_size() argument
128 return ((issue->value & BIO_ISSUE_SIZE_MASK) >> BIO_ISSUE_SIZE_SHIFT); in bio_issue_size()
131 static inline void bio_issue_init(struct bio_issue *issue, in bio_issue_init() argument
135 issue->value = ((issue->value & BIO_ISSUE_RES_MASK) | in bio_issue_init()
|
| /Linux-v5.4/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
|
| D | sysfs-fs-f2fs | 32 Controls the issue rate of segment discard commands.
78 Controls the issue rate of small discard commands.
85 will not issue discards with size that is smaller than granularity.
93 Set timeout to issue discard commands during umount.
|
| /Linux-v5.4/samples/bpf/ |
| D | xdp_rxq_info_kern.c | 36 __u64 issue; member
101 rec->issue++; in xdp_prognum0()
116 rxq_rec->issue++; in xdp_prognum0()
|
| D | xdp_redirect_cpu_kern.c | 32 __u64 issue; member
223 rec->issue++; in xdp_prognum0_no_touch()
266 rec->issue++; in xdp_prognum1_touch_data()
314 rec->issue++; in xdp_prognum2_round_robin()
382 rec->issue++; in xdp_prognum3_proto_separate()
458 rec->issue++; in xdp_prognum4_ddos_filter_pktgen()
561 rec->issue++; in xdp_prognum5_lb_hash_ip_pairs()
681 rec->issue += 1; in trace_xdp_cpumap_enqueue()
718 rec->issue++; in trace_xdp_cpumap_kthread()
|
| D | xdp_rxq_info_user.c | 185 __u64 issue; member
283 rec->cpu[i].issue = values[i].issue; in map_collect_percpu()
284 sum_issue += values[i].issue; in map_collect_percpu()
287 rec->total.issue = sum_issue; in map_collect_percpu()
335 packets = r->issue - p->issue; in calc_errs_pps()
|
| D | xdp_redirect_cpu_user.c | 149 __u64 issue; member
188 rec->cpu[i].issue = values[i].issue; in map_collect_percpu()
189 sum_issue += values[i].issue; in map_collect_percpu()
193 rec->total.issue = sum_issue; in map_collect_percpu()
290 packets = r->issue - p->issue; in calc_errs_pps()
|
| /Linux-v5.4/Documentation/networking/device_drivers/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
|
| /Linux-v5.4/drivers/gpu/drm/panfrost/ |
| D | panfrost_issues.h | 171 enum panfrost_hw_issue issue) in panfrost_has_hw_issue() argument
173 return test_bit(issue, pfdev->features.hw_issues); in panfrost_has_hw_issue()
|
| D | TODO | 6 - Bifrost specific feature and issue handling
|
| /Linux-v5.4/Documentation/process/ |
| D | embargoed-hardware-issues.rst | 34 issue according to our documented process.
94 will form the initial response team for a particular issue. The initial
96 the issue in the best technical way.
100 immediate exclusion from the current issue and removal from all related
134 issue after confirming with the developers that they will adhere to this
137 issue after initial contact. The hardware security team is supporting the
147 entities who have already been, or should be, informed about the issue.
156 - If an expert which is required to handle an issue is employed by an
238 disclosure of a particular issue, unless requested by a response team or by
|
| /Linux-v5.4/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
|
| /Linux-v5.4/drivers/staging/speakup/ |
| D | TODO | 11 The first issue has to do with the way speakup communicates with serial
34 Another issue seems to only happen on SMP systems. It seems
|
| /Linux-v5.4/arch/alpha/lib/ |
| D | strlen.S | 35 nop # helps dual issue last two insns
|
| /Linux-v5.4/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 | 218 u64 now, issue = READ_ONCE(rwb->sync_issue); in rwb_sync_issue_lat() local
220 if (!issue || !rwb->sync_cookie) in rwb_sync_issue_lat()
224 return now - issue; in rwb_sync_issue_lat()
808 .issue = wbt_issue,
|
| /Linux-v5.4/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
|
| /Linux-v5.4/net/rxrpc/ |
| D | rxkad.c | 908 time64_t issue, now; in rxkad_decrypt_ticket() local
1004 issue = rxrpc_u32_to_time64(le32_to_cpu(stamp)); in rxkad_decrypt_ticket()
1008 issue = rxrpc_u32_to_time64(be32_to_cpu(stamp)); in rxkad_decrypt_ticket()
1012 _debug("KIV ISSUE: %llx [%llx]", issue, now); in rxkad_decrypt_ticket()
1015 if (issue > now) { in rxkad_decrypt_ticket()
1021 if (issue < now - life) { in rxkad_decrypt_ticket()
1027 *_expiry = issue + life; in rxkad_decrypt_ticket()
|
