Searched full:issue (Results 1 – 25 of 323) sorted by relevance
12345678910>>...13
| /Documentation/kbuild/ |
| 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 | issues.rst | 5 issue #1
8 .. literalinclude:: Kconfig.recursion-issue-01
11 issue #2
14 .. literalinclude:: Kconfig.recursion-issue-02
|
| 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 | 606 into a recursive dependency issue with Kconfig, a recursive dependency can be
612 Kconfig recursive issue" subsection below. Kconfig does not do recursive
619 Simple Kconfig recursive issue
622 Read: Documentation/kbuild/Kconfig.recursion-issue-01
626 make KBUILD_KCONFIG=Documentation/kbuild/Kconfig.recursion-issue-01 allnoconfig
628 Cumulative Kconfig recursive issue
631 Read: Documentation/kbuild/Kconfig.recursion-issue-02
635 make KBUILD_KCONFIG=Documentation/kbuild/Kconfig.recursion-issue-02 allnoconfig
637 Practical solutions to kconfig recursive issue
640 Developers who run into the recursive Kconfig issue have two options
[all …]
|
| /Documentation/admin-guide/ |
| D | reporting-issues.rst | 16 <https://kernel.org/>`_. If it still shows the issue, report it to the stable
22 issue. Check the :ref:`MAINTAINERS <maintainers>` file for how its developers
27 <https://kernel.org/>`_. If the issue is present there, send a report.
29 The issue was fixed there, but you would like to see it resolved in a still
38 before the issue occurs.
42 issue, like the kernel and the distro used. In case of a regression, CC the
64 early if an issue that looks like a Linux kernel problem is actually caused by
68 * Are you facing an issue with a Linux kernel a hardware or software vendor
70 document and reporting the issue to your vendor instead, unless you are
79 * See if the issue you are dealing with qualifies as regression, security
[all …]
|
| D | reporting-regressions.rst | 24 #. Report your issue as outlined in Documentation/admin-guide/reporting-issues.rst,
31 Linux kernel regression tracking bot "regzbot" track the issue by specifying
52 the issue.
76 Just report the issue as outlined in
115 v5.14-rc1 was the first version where you encountered the issue. If you
161 time-consuming to reliably reproduce the issue, consider teaming up with other
169 issue might better be dealt with in private, feel free to omit the list.
222 running into the issue; nevertheless developers need to take enough time and
229 Is it a regression, if the issue can be avoided by updating some software?
268 developers of the affected code area should look into the issue to find a fix
[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
|
| /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/process/ |
| D | embargoed-hardware-issues.rst | 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
141 issue after confirming with the developers that they will adhere to this
144 issue after initial contact. The hardware security team is supporting the
154 entities who have already been, or should be, informed about the issue.
163 - If an expert who is required to handle an issue is employed by a listed
218 List participants may not communicate about the issue outside of the
286 disclosure of a particular issue, unless requested by a response team or by
|
| D | handling-regressions.rst | 26 #. Make the Linux kernel regression tracking bot "regzbot" track the issue (this
32 when the issue started to happen::
44 description pointing to all places where the issue was reported, as
47 only fixing part of the issue that caused the regression, you may use
82 "regzbot" immediately start tracking the issue:
90 This tells regzbot the version range in which the issue started to happen;
118 * Point to all places where the issue was reported using "Closes:" tags::
123 If you are only fixing part of the issue, you may use "Link:" instead as
134 into the issue weeks, months, or years later. These tags are also crucial for
152 should be less than two. And it ought to be just a few days, if the issue is
[all …]
|
| D | cve.rst | 49 feel you have found an unfixed security issue, please follow the
57 have a CVE assigned before an issue is resolved with a commit, please
61 No CVEs will be assigned for any issue found in a version of the kernel
82 If a security issue is found in a Linux kernel that is only supported by
|
| D | security-bugs.rst | 31 issue if all the details are hidden away in attachments. Think of it like a
86 of a potential security issue you DO NOT contact the "linux-distros"
102 assigned for a confirmed issue, they can contact the :doc:`kernel CVE
|
| /Documentation/admin-guide/hw-vuln/ |
| D | cross-thread-rsb.rst | 29 The following CVE entry is related to this issue:
75 Both mitigations are required to fully address this issue.
85 By default, the KVM hypervisor mitigates this issue by intercepting guest
|
| /Documentation/hwmon/ |
| D | asus_wmi_sensors.rst | 71 getting stuck. This is not an issue with the driver, but the BIOS. The Prime
77 rectify the issue.
|
| /Documentation/networking/device_drivers/ethernet/intel/ |
| D | ixgbevf.rst | 60 If an issue is identified with the released source code on a supported kernel
61 with a supported adapter, email the specific information related to the issue
|
| D | igbvf.rst | 58 If an issue is identified with the released source code on a supported kernel
59 with a supported adapter, email the specific information related to the issue
|
| D | idpf.rst | 76 enabling flow control may mitigate the issue.
150 If an issue is identified with the released source code on a supported kernel
151 with a supported adapter, email the specific information related to the issue
|
| /Documentation/gpu/amdgpu/display/ |
| D | dc-debug.rst | 84 an issue arises is some generic timeout error. So, to get more relevant
109 Lastly, after you are able to reproduce the issue you are trying to debug,
116 enabling the relevant bits in the mask before reproducing the issue and
|
| /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/networking/ |
| D | mptcp-sysctl.rst | 41 when a MPTCP firewall blackhole issue happens. This time period will
44 blackhole issue goes away.
|
| /Documentation/devicetree/bindings/spi/ |
| D | brcm,bcm63xx-hsspi.yaml | 25 terminate the transaction to some SPI devices prematurely. The issue can be
32 select explicitly. This solves the issue in the old controller.
|
| /Documentation/filesystems/bcachefs/ |
| D | CodingStyle.rst | 67 issue is that we don't know where the issue is because we can't see what's
88 the issue. It's worth putting effort into them.
105 rush to fix the initial issue. Look for things that will make related bugs
|
| /Documentation/devicetree/bindings/serial/ |
| D | nvidia,tegra20-hsuart.yaml | 72 issue. UART RX baud rate tolerance level is 0% to +4% in 1-stop config. Otherwise, the
82 Tegra UART is expected to handle it. Due to the issue stated above, baud rate on Tegra UART
|
| /Documentation/security/ |
| D | ipe.rst | 15 The original issue that prompted IPE's implementation was the creation
45 presented an issue: EVM would protect the label, but if an attacker could
153 The first issue is one of code maintenance and duplication. To author policies,
169 this quickly becomes an issue, as stale policies from years ago may be present,
178 The second issue with a binary format is one of transparency. As IPE controls
284 The issue of implicit actions only becomes visible when you consider
304 issue becomes with the second requirement about specific data files.
|
12345678910>>...13