| /linux-6.15/io_uring/ |
| H A D | opdef.c | 59 .issue = io_nop,
74 .issue = io_read,
89 .issue = io_write,
95 .issue = io_fsync,
228 .issue = io_close,
239 .issue = io_statx,
253 .issue = io_read,
267 .issue = io_write,
290 .issue = io_send,
305 .issue = io_recv,
[all …]
|
| H A D | opdef.h | 34 int (*issue)(struct io_kiocb *, unsigned int); member
|
| /linux-6.15/Documentation/kbuild/ |
| H A D | issues.rst | 5 issue #1
8 .. literalinclude:: Kconfig.recursion-issue-01
11 issue #2
14 .. literalinclude:: Kconfig.recursion-issue-02
|
| H A 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"
|
| H A 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
|
| H A 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"
|
| /linux-6.15/arch/arm64/boot/dts/rockchip/ |
| H A D | rk3588-jaguar-pre-ict-tester.dtso | 79 * but GPIO3_C6 would catch this HW soldering issue.
83 * issue. Therefore, let's enforce a pull-up (which is
92 * the loop doesn't exist on HW (soldering issue on
101 * but GPIO3_C6 would catch this HW soldering issue.
103 * LOW. This is an issue if GPIO3_B2 isn't properly
104 * routed due to soldering issue, because GPIO3_B2
116 * properly routed due to soldering issue, because
135 * the loop doesn't exist on HW (soldering issue on
145 * the loop doesn't exist on HW (soldering issue on
155 * the loop doesn't exist on HW (soldering issue on
[all …]
|
| /linux-6.15/Documentation/admin-guide/ |
| H A D | reporting-issues.rst | 38 before the issue occurs.
371 need to report your issue". The developers that should take care of the issue
426 potential kernel issue.
547 Document how to reproduce issue
833 using it for reproducing the issue is also better than not reporting it issue
857 unsuitable for testing and issue reporting: the changes might cause the issue
907 the issue at all.
1110 issue and its environment. What's actually needed depends a lot on the issue,
1148 changed just to fix your issue.
1384 issue.
[all …]
|
| /linux-6.15/Documentation/ABI/testing/ |
| H A 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
|
| /linux-6.15/Documentation/gpu/amdgpu/display/ |
| H A D | dc-debug.rst | 14 section equips users to determine if a specific issue was caused by the display
44 issue. If you do not see that line, something else might have failed before
46 display issue.
117 If you can boot your system with the DC disabled and still see the issue, it
120 issue. In some scenarios, disabling DC is impossible since it might be
121 necessary to use the display component to reproduce the issue (e.g., play a
137 is less likely that the issue is related to power management. If the issue
157 that the issue is likely on the the driver side. If you can still see the
158 problem in the data collected, it is an issue that probably happened during
271 an issue arises is some generic timeout error. So, to get more relevant
[all …]
|
| /linux-6.15/rust/pin-init/ |
| H A D | CONTRIBUTING.md | 13 For any type of bug report, please submit an issue using the bug report issue template.
15 If the issue is a soundness issue, please privately report it as a security vulnerability via the
20 If you have any feature requests, please submit an issue using the feature request issue template.
|
| /linux-6.15/samples/bpf/ |
| H A D | xdp_sample.bpf.c | 146 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()
|
| H A D | xdp_sample_shared.h | 8 size_t issue; member
|
| /linux-6.15/drivers/gpu/drm/ci/xfails/ |
| H A D | msm-sdm845-skips.txt | 4 # Failing due to a bootloader/fw issue. The workaround in mesa CI involves these two patches
34 # IGT issue. is_joiner_mode() should return false for non-Intel hardware.
|
| /linux-6.15/block/ |
| H A D | blk.h | 697 static inline u64 bio_issue_time(struct bio_issue *issue) in bio_issue_time() argument
699 return __bio_issue_time(issue->value); in bio_issue_time()
702 static inline sector_t bio_issue_size(struct bio_issue *issue) in bio_issue_size() argument
704 return ((issue->value & BIO_ISSUE_SIZE_MASK) >> BIO_ISSUE_SIZE_SHIFT); in bio_issue_size()
707 static inline void bio_issue_init(struct bio_issue *issue, in bio_issue_init() argument
711 issue->value = ((issue->value & BIO_ISSUE_RES_MASK) | in bio_issue_init()
|
| /linux-6.15/drivers/gpu/drm/panfrost/ |
| H A D | panfrost_issues.h | 269 enum panfrost_hw_issue issue) in panfrost_has_hw_issue() argument
271 return test_bit(issue, pfdev->features.hw_issues); in panfrost_has_hw_issue()
|
| H A D | TODO | 6 - Bifrost specific feature and issue handling
|
| /linux-6.15/Documentation/networking/device_drivers/ethernet/intel/ |
| H A 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
|
| H A 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
|
| /linux-6.15/Documentation/admin-guide/hw-vuln/ |
| H A 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
|
| /linux-6.15/Documentation/driver-api/soundwire/ |
| H A 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-6.15/Documentation/process/ |
| H A D | handling-regressions.rst | 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:
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
173 resolving an issue then might take longer than outlined below.
286 maintainer to mention the issue in his mainline pull request.
308 issue might better be dealt with in private, feel free to omit the list.
762 previously benign behavior of that old issue.
[all …]
|
| /linux-6.15/Documentation/hwmon/ |
| H A 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.
|
| /linux-6.15/Documentation/process/debugging/ |
| H A D | index.rst | 38 Depending on the issue, a different set of tools is available to track down the
41 As a first step you have to figure out what kind of issue you want to debug.
|
| /linux-6.15/drivers/virt/coco/pkvm-guest/ |
| H A D | Kconfig | 6 are isolated from the host and must issue hypercalls to enable
|