Searched full:issue (Results 1 – 25 of 226) sorted by relevance
12345678910
| /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 …]
|
| /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.
84 Controls the issue rate of small discard commands.
91 will not issue discards with size that is smaller than granularity.
99 Set timeout to issue discard commands during umount.
|
| D | rtc-cdev | 22 powerful interface, which can issue alarms beyond 24 hours and
|
| /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
|
| D | stable-kernel-rules.rst | 16 security issue, or some "oh, that's not good" issue. In short, something
19 be considered if they fix a notable performance or interactivity issue.
|
| /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
|
| /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
|
| D | ixgb.rst | 382 Cable Interoperability Issue with Fujitsu XENPAK Module in SmartBits Chassis
389 cable assembly may resolve the issue.
396 the issue.
401 this situation occurs, using a different cable assembly may resolve the issue.
421 the available memory is heavily fragmented. This issue may be seen with PCI-X
443 UDP Stress Test Dropped Packet Issue
466 If an issue is identified with the released source code on a supported kernel
467 with a supported adapter, email the specific information related to the issue
|
| D | iavf.rst | 78 To enable/disable VLAN tag stripping for a VF, issue the following command
231 active slave. Linux bonding will fail at this point. This issue will not occur
255 errors to stdout. Use a maximum of three queues to avoid this issue.
270 all of the virtual ports. The following command may work around the issue::
329 If an issue is identified with the released source code on the supported kernel
330 with a supported adapter, email the specific information related to the issue
|
| /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
|
| D | slave-device.txt | 22 quality issue or the host processor can't support higher
|
| /Documentation/usb/ |
| D | ehci.rst | 117 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
|
| /Documentation/admin-guide/ |
| D | reporting-bugs.rst | 31 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
|
| /Documentation/driver-api/firmware/ |
| D | direct-fs-lookup.rst | 23 available. Stuffing the firmware into initramfs resolves this race issue,
|
| /Documentation/s390/ |
| D | 3270.rst | 177 above? Use the grep command to find out; for instance, issue
183 issue "ls -l /dev/3270/tty620". The output should start with the
193 If so, you must issue the command "DEF GRAF 620" from your VM
282 Have a command you issue frequently? Assign it to a PF or PA key! Use
|
| /Documentation/admin-guide/hw-vuln/ |
| D | multihit.rst | 29 The following CVE entry is related to this issue:
82 - Software changes mitigate this issue.
91 and will be set on CPU's which are mitigated against this issue.
|
| /Documentation/ |
| D | atomic_bitops.txt | 41 In particular __clear_bit_unlock() suffers the same issue as atomic_set(),
|
| /Documentation/networking/ |
| D | hinic.txt | 123 If an issue is identified with the released source code on the supported kernel
124 with a supported adapter, email the specific information related to the issue to
|
12345678910