Home
last modified time | relevance | path

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

12345678910>>...14

/linux/Documentation/kbuild/
A Dissues.rst5 issue #1
8 .. literalinclude:: Kconfig.recursion-issue-01
11 issue #2
14 .. literalinclude:: Kconfig.recursion-issue-02
A 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"
A 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
A 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"
A Dkconfig-language.rst580 into a recursive dependency issue with Kconfig, a recursive dependency can be
586 Kconfig recursive issue" subsection below. Kconfig does not do recursive
593 Simple Kconfig recursive issue
596 Read: Documentation/kbuild/Kconfig.recursion-issue-01
600 make KBUILD_KCONFIG=Documentation/kbuild/Kconfig.recursion-issue-01 allnoconfig
602 Cumulative Kconfig recursive issue
605 Read: Documentation/kbuild/Kconfig.recursion-issue-02
611 Practical solutions to kconfig recursive issue
614 Developers who run into the recursive Kconfig issue have two options
626 Documentation/kbuild/Kconfig.recursion-issue-01 through the removal
[all …]
/linux/Documentation/admin-guide/
A Dreporting-issues.rst47 before the issue occurs.
380 need to report your issue". The developers that should take care of the issue
441 potential kernel issue.
562 Document how to reproduce issue
848 using it for reproducing the issue is also better than not reporting it issue
872 unsuitable for testing and issue reporting: the changes might cause the issue
922 the issue at all.
1124 issue and its environment. What's actually needed depends a lot on the issue,
1162 changed just to fix your issue.
1398 issue.
[all …]
/linux/include/linux/
A Dblk_types.h211 static inline u64 bio_issue_time(struct bio_issue *issue) in bio_issue_time() argument
213 return __bio_issue_time(issue->value); in bio_issue_time()
216 static inline sector_t bio_issue_size(struct bio_issue *issue) in bio_issue_size() argument
218 return ((issue->value & BIO_ISSUE_SIZE_MASK) >> BIO_ISSUE_SIZE_SHIFT); in bio_issue_size()
221 static inline void bio_issue_init(struct bio_issue *issue, in bio_issue_init() argument
225 issue->value = ((issue->value & BIO_ISSUE_RES_MASK) | in bio_issue_init()
/linux/Documentation/ABI/testing/
A 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/samples/bpf/
A Dxdp_rxq_info_kern.c37 __u64 issue; member
102 rec->issue++; in xdp_prognum0()
117 rxq_rec->issue++; in xdp_prognum0()
A Dxdp_rxq_info_user.c185 __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()
A Dxdp_sample.bpf.c146 NO_TEAR_INC(rec->issue); in BPF_PROG()
176 NO_TEAR_INC(rec->issue); in BPF_PROG()
232 NO_TEAR_INC(rec->issue); in BPF_PROG()
264 NO_TEAR_INC(rec->issue); in BPF_PROG()
A Dxdp_redirect_cpu.bpf.c163 NO_TEAR_INC(rec->issue); in xdp_prognum0_no_touch()
205 NO_TEAR_INC(rec->issue); in xdp_prognum1_touch_data()
250 NO_TEAR_INC(rec->issue); in xdp_prognum2_round_robin()
316 NO_TEAR_INC(rec->issue); in xdp_prognum3_proto_separate()
389 NO_TEAR_INC(rec->issue); in xdp_prognum4_ddos_filter_pktgen()
490 NO_TEAR_INC(rec->issue); in xdp_prognum5_lb_hash_ip_pairs()
A Dxdp_sample_shared.h8 size_t issue; member
/linux/drivers/gpu/drm/panfrost/
A Dpanfrost_issues.h252 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()
A DTODO6 - Bifrost specific feature and issue handling
/linux/Documentation/process/
A Dembargoed-hardware-issues.rst36 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
/linux/Documentation/driver-api/soundwire/
A 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/Documentation/networking/device_drivers/ethernet/intel/
A Digbvf.rst63 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
A Dixgbevf.rst65 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/block/
A Dblk-rq-qos.c53 if (rqos->ops->issue) in __rq_qos_issue()
54 rqos->ops->issue(rqos, rq); in __rq_qos_issue()
A Dblk-wbt.c219 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()
807 .issue = wbt_issue,
/linux/Documentation/powerpc/
A Dqe_firmware.rst87 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/Documentation/devicetree/bindings/serial/
A Dnvidia,tegra20-hsuart.txt39 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/arch/alpha/lib/
A Dstrlen.S35 nop # helps dual issue last two insns
/linux/Documentation/usb/
A Dehci.rst117 the EHCI controller can issue interrupts.
160 Bulk transfers are most often used where throughput is an issue. It's
180 onto one bus does not get you 60 MByte/sec. The issue appears to be
195 you issue a control or bulk request you can often expect to learn that
225 transfers are fully scheduled, so the main issue is likely to be how

Completed in 41 milliseconds

12345678910>>...14