Home
last modified time | relevance | path

Searched refs:issue (Results 1 – 25 of 258) sorted by relevance

1234567891011

/Linux-v4.19/Documentation/kbuild/
DKconfig.recursion-issue-011 # 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"
DKconfig.recursion-issue-021 # 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
DKconfig.select-break1 # Select broken dependency issue
13 # example of this issue is below.
21 mainmenu "Simple example to demo kconfig select broken dependency issue"
Dkconfig-language.txt514 into a recursive dependency issue with Kconfig, a recursive dependency can be
520 Kconfig recursive issue" subsection below. Kconfig does not do recursive
527 Simple Kconfig recursive issue
530 Read: Documentation/kbuild/Kconfig.recursion-issue-01
534 make KBUILD_KCONFIG=Documentation/kbuild/Kconfig.recursion-issue-01 allnoconfig
536 Cumulative Kconfig recursive issue
539 Read: Documentation/kbuild/Kconfig.recursion-issue-02
543 make KBUILD_KCONFIG=Documentation/kbuild/Kconfig.recursion-issue-02 allnoconfig
545 Practical solutions to kconfig recursive issue
548 Developers who run into the recursive Kconfig issue have two options
[all …]
/Linux-v4.19/include/linux/
Dblk_types.h121 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-v4.19/Documentation/ABI/testing/
Dsysfs-bus-usb-lvstest9 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
/Linux-v4.19/samples/bpf/
Dxdp_rxq_info_kern.c36 __u64 issue; member
101 rec->issue++; in xdp_prognum0()
116 rxq_rec->issue++; in xdp_prognum0()
Dxdp_redirect_cpu_kern.c32 __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()
Dxdp_rxq_info_user.c170 __u64 issue; member
268 rec->cpu[i].issue = values[i].issue; in map_collect_percpu()
269 sum_issue += values[i].issue; in map_collect_percpu()
272 rec->total.issue = sum_issue; in map_collect_percpu()
320 packets = r->issue - p->issue; in calc_errs_pps()
Dxdp_redirect_cpu_user.c117 __u64 issue; member
156 rec->cpu[i].issue = values[i].issue; in map_collect_percpu()
157 sum_issue += values[i].issue; in map_collect_percpu()
161 rec->total.issue = sum_issue; in map_collect_percpu()
258 packets = r->issue - p->issue; in calc_errs_pps()
/Linux-v4.19/drivers/net/ethernet/xilinx/
Dxilinx_axienet_mdio.c169 goto issue; in axienet_mdio_setup()
178 goto issue; in axienet_mdio_setup()
194 issue: in axienet_mdio_setup()
/Linux-v4.19/Documentation/networking/
Dixgbevf.txt50 If an issue is identified with the released source code on the supported
52 to the issue to e1000-devel@lists.sf.net
Di40evf.txt52 If an issue is identified with the released source code on the supported
54 to the issue to e1000-devel@lists.sf.net
Digbvf.txt78 If an issue is identified with the released source code on the supported
80 to the issue to e1000-devel@lists.sf.net
Dice.txt38 If an issue is identified with the released source code, please email
/Linux-v4.19/block/
Dblk-rq-qos.c55 if (rqos->ops->issue) in rq_qos_issue()
56 rqos->ops->issue(rqos, rq); in rq_qos_issue()
Dblk-wbt.c217 u64 now, issue = READ_ONCE(rwb->sync_issue); in rwb_sync_issue_lat() local
219 if (!issue || !rwb->sync_cookie) in rwb_sync_issue_lat()
223 return now - issue; in rwb_sync_issue_lat()
771 .issue = wbt_issue,
/Linux-v4.19/Documentation/driver-api/soundwire/
Derror_handling.rst25 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-v4.19/drivers/staging/speakup/
DTODO11 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-v4.19/arch/alpha/lib/
Dstrlen.S35 nop # helps dual issue last two insns
/Linux-v4.19/Documentation/arm/SA1100/
DPangolin7 To compile for Pangolin, you must issue the following commands:
/Linux-v4.19/net/rxrpc/
Drxkad.c876 time64_t issue, now; in rxkad_decrypt_ticket() local
972 issue = rxrpc_u32_to_time64(le32_to_cpu(stamp)); in rxkad_decrypt_ticket()
976 issue = rxrpc_u32_to_time64(be32_to_cpu(stamp)); in rxkad_decrypt_ticket()
980 _debug("KIV ISSUE: %llx [%llx]", issue, now); in rxkad_decrypt_ticket()
983 if (issue > now) { in rxkad_decrypt_ticket()
989 if (issue < now - life) { in rxkad_decrypt_ticket()
995 *_expiry = issue + life; in rxkad_decrypt_ticket()
/Linux-v4.19/Documentation/powerpc/
Dqe_firmware.txt87 flexibility and save h/w traps If new features are activated or an issue is
134 | | RX INIT | command, the host must issue another special|
136 | | | following that re-issue the ATM RX INIT |
146 | | | must issue another command. |
157 | | command | INIT command, user must issue this command |
/Linux-v4.19/Documentation/admin-guide/
Dreporting-bugs.rst31 Identifying which part of the Linux kernel might be causing your issue
36 Instead, try to figure out which kernel subsystem is causing the issue,
45 Once you know the subsystem that is causing the issue, you should send a
66 If you can't figure out which subsystem caused the issue, you should file
/Linux-v4.19/Documentation/usb/
Dehci.txt109 the EHCI controller can issue interrupts.
148 Bulk transfers are most often used where throughput is an issue. It's
167 onto one bus does not get you 60 MByte/sec. The issue appears to be
182 you issue a control or bulk request you can often expect to learn that
210 transfers are fully scheduled, so the main issue is likely to be how

1234567891011