Searched refs:breaks (Results 1 – 25 of 31) sorted by relevance
12
/Linux-v5.4/tools/testing/selftests/powerpc/ptrace/ |
D | perf-hwbreak.c | 80 unsigned long long breaks, needed; in runtestsingle() local 130 res = read(break_fd, &breaks, sizeof(unsigned long long)); in runtestsingle() 140 (unsigned long int)ptr, breaks, loop_num, readwriteflag, exclude_user, arraytest); in runtestsingle() 141 if (breaks != needed) { in runtestsingle() 143 (unsigned long int)ptr, breaks, needed, loop_num, readwriteflag, exclude_user); in runtestsingle()
|
/Linux-v5.4/Documentation/ |
D | debugging-modules.txt | 6 "succeed" in this case is hacky and breaks some setups, and also we
|
/Linux-v5.4/Documentation/kbuild/ |
D | Kconfig.select-break | 18 # Kconfig does not visit the dependencies, it breaks the dependencies of B
|
/Linux-v5.4/Documentation/devicetree/bindings/regulator/ |
D | vctrl.txt | 25 avoid this situation the vctrl driver breaks down
|
/Linux-v5.4/Documentation/process/ |
D | email-clients.rst | 33 and unwanted line breaks. 52 This breaks many scripts that read and apply the patches. 318 At the same time it wraps lines every 78 chars with CRLF style line breaks
|
D | 7.AdvancedTopics.rst | 70 development history. An inconvenient patch (one which breaks bisection,
|
D | 1.Intro.rst | 150 to also fix any code that breaks as the result of that change. So code
|
D | 4.Coding.rst | 203 breaks? The best answer to this question was expressed by Linus in July,
|
D | coding-style.rst | 95 printk messages, because that breaks the ability to grep for them.
|
/Linux-v5.4/arch/xtensa/kernel/ |
D | signal.c | 296 # error Generating the MOVI instruction below breaks! in gen_return_code()
|
/Linux-v5.4/Documentation/driver-api/ |
D | dell_rbu.rst | 34 using the driver breaks the image in to packets of fixed sizes and the driver
|
/Linux-v5.4/Documentation/input/devices/ |
D | ntrig.rst | 46 see breaks in lines during drawing, or drop an object during a long drag.
|
/Linux-v5.4/Documentation/RCU/ |
D | UP.rst | 91 Permitting call_rcu() to immediately invoke its arguments breaks RCU,
|
/Linux-v5.4/Documentation/doc-guide/ |
D | kernel-doc.rst | 145 line breaks, so if you try to format some text nicely, as in:: 156 So, in order to produce the desired line breaks, you need to use a
|
/Linux-v5.4/Documentation/hwmon/ |
D | lm90.rst | 301 * Extended temperature range (breaks compatibility)
|
/Linux-v5.4/Documentation/admin-guide/hw-vuln/ |
D | l1tf.rst | 58 While Meltdown breaks the user space to kernel space protection, L1TF 89 The fact that L1TF breaks all domain protections allows malicious guest
|
/Linux-v5.4/drivers/iommu/ |
D | Kconfig | 381 even fewer good ones. If saying YES here breaks your board
|
/Linux-v5.4/Documentation/devicetree/bindings/arm/ |
D | idle-states.txt | 200 IDLE1 and IDLE2 states breaks even.
|
/Linux-v5.4/Documentation/gpu/ |
D | todo.rst | 175 that it uses some fields in struct page itself, which breaks shmem gem objects
|
/Linux-v5.4/Documentation/vm/ |
D | hugetlbfs_reserv.rst | 564 * When cpuset is configured, it breaks the strict hugetlb page
|
/Linux-v5.4/Documentation/filesystems/ |
D | sharedsubtree.txt | 896 The overall algorithm breaks the operation into 3 phases: (look at
|
/Linux-v5.4/Documentation/scsi/ |
D | ChangeLog.sym53c8xx | 589 core is performing SCSI selection breaks the selection procedure
|
/Linux-v5.4/Documentation/admin-guide/sysctl/ |
D | kernel.rst | 983 destroy an unattached segment. Of course, this breaks the way things are
|
/Linux-v5.4/Documentation/media/uapi/v4l/ |
D | hist-v4l2.rst | 289 removed. This change *breaks compatibility* with earlier versions:
|
/Linux-v5.4/Documentation/networking/ |
D | can.rst | 369 and up to 64 bytes of payload. This extended payload length breaks all the
|
12