| /linux/fs/ocfs2/dlm/ |
| H A D | dlmast.c | 264 struct dlm_proxy_ast *past = (struct dlm_proxy_ast *) msg->buf; in dlm_proxy_ast_handler() local
279 name = past->name; in dlm_proxy_ast_handler()
280 locklen = past->namelen; in dlm_proxy_ast_handler()
281 cookie = past->cookie; in dlm_proxy_ast_handler()
282 flags = be32_to_cpu(past->flags); in dlm_proxy_ast_handler()
283 node = past->node_idx; in dlm_proxy_ast_handler()
303 mlog(0, "type=%d, blocked_type=%d\n", past->type, past->blocked_type); in dlm_proxy_ast_handler()
305 if (past->type != DLM_AST && in dlm_proxy_ast_handler()
306 past->type != DLM_BAST) { in dlm_proxy_ast_handler()
308 "name=%.*s, node=%u\n", past->type, in dlm_proxy_ast_handler()
[all …]
|
| /linux/drivers/gpu/drm/i915/ |
| H A D | TODO.txt | 6 improved a lot the past 2 years, there's no reason anymore not to use it.
12 - There's a lot of complexity added past few years to make relocations faster.
16 2. Any complexity added in this area past few years which can't be justified
|
| /linux/tools/kvm/kvm_stat/ |
| H A D | kvm_stat.txt | 90 --debugfs-include-past::
91 include all available data on past events for debugfs
|
| /linux/Documentation/userspace-api/media/dvb/ |
| H A D | examples.rst | 9 In the past, we used to have a set of examples here. However, those
|
| H A D | dvbproperty.rst | 16 In the past (up to DVB API version 3 - DVBv3), the strategy used was to have a
|
| /linux/tools/thermal/tmon/ |
| H A D | README | 6 thermal relationship between processor and fan has become past for modern
|
| /linux/Documentation/filesystems/ext4/ |
| H A D | verity.rst | 40 Verity files cannot have blocks allocated past the end of the verity
|
| H A D | group_descr.rst | 96 - Lower 16-bits of unused inode count. If set, we needn't scan past the
|
| /linux/Documentation/fb/ |
| H A D | pvr2fb.rst | 61 XF86_FBDev has been shown to work on the Dreamcast in the past - though not yet
|
| /linux/Documentation/ABI/stable/ |
| H A D | sysfs-firmware-opal-elog | 29 from the queue that was generated some time in the past.
|
| /linux/tools/testing/selftests/coredump/ |
| H A D | README.rst | 24 However, this was broken in the past and `kstkesp` was zero even during coredump:
|
| /linux/Documentation/networking/ |
| H A D | netif-msg.rst | 21 The message level was not precisely defined past level 3, but were
|
| /linux/arch/powerpc/kernel/vdso/ |
| H A D | sigtramp64.S | 304 # we ever have some call chain that returns somewhere past the addi?
|
| /linux/Documentation/admin-guide/thermal/ |
| H A D | intel_powerclamp.rst | 127 cannot be based on the past or current input. Therefore, the
135 past samples and outputs are included in the feedback. For example, a
138 derivative gains of the past samples.
|
| /linux/arch/mips/lib/ |
| H A D | memcpy.S | 406 ADD t1, dst, len # t1 is just past last byte of dst
569 LOADK t0, THREAD_BUADDR(t0) # t0 is just past last good address
|
| /linux/Documentation/filesystems/ |
| H A D | fiemap.rst | 78 length to extend past the request. Unless FIEMAP_EXTENT_NOT_ALIGNED is
103 This is generally the last extent in the file. A mapping attempt past
|
| H A D | cramfs.rst | 25 filesystem is allowed to extend past 256MB.)
|
| /linux/Documentation/process/ |
| H A D | kernel-driver-statement.rst | 24 today, have in the past, or will in the future.
|
| H A D | kernel-enforcement-statement.rst | 53 we might work for today, have in the past, or will in the future.
|
| H A D | botching-up-ioctls.rst | 9 One clear insight kernel graphics hackers gained in the past few years is that
63 past) then you need a driver feature flag or revision number somewhere.
|
| /linux/Documentation/devicetree/ |
| H A D | overlay-notes.rst | 128 or its content but these pointers must not persist past the notifier callback
|
| /linux/Documentation/locking/ |
| H A D | lockdep-design.rst | 176 took any hardirq-unsafe lock in the past.
179 any softirq-unsafe lock in the past.
182 hardirq-safe lock took it in the past.
185 softirq-safe lock took it in the past.
|
| /linux/Documentation/security/ |
| H A D | self-protection.rst | 154 The classic stack buffer overflow involves writing past the expected end
192 traditionally leads to being able to write past the end of kernel buffers.
|
| /linux/Documentation/dev-tools/kunit/ |
| H A D | faq.rst | 84 filesystem mounted), and has had issues in the past when built statically and
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-block-bcache | 47 For backing devices: Threshold past which sequential IO will
|