| /OK3568_Linux_fs/kernel/include/trace/events/ |
| H A D | cachefiles.h | 74 enum cachefiles_obj_ref_trace why, 77 TP_ARGS(obj, cookie, why, usage), 83 __field(enum cachefiles_obj_ref_trace, why ) 91 __entry->why = why; 96 __print_symbolic(__entry->why, cachefiles_obj_ref_traces)) 169 enum fscache_why_object_killed why), 171 TP_ARGS(obj, de, why), 177 __field(enum fscache_why_object_killed, why ) 183 __entry->why = why; 188 __print_symbolic(__entry->why, cachefiles_obj_kill_traces)) [all …]
|
| H A D | rxrpc.h | 703 TP_PROTO(unsigned int call_nr, const char *why, u32 cid, u32 call_id, 706 TP_ARGS(call_nr, why, cid, call_id, seq, abort_code, error), 710 __array(char, why, 4 ) 719 memcpy(__entry->why, why, 4); 731 __entry->abort_code, __entry->error, __entry->why) 761 TP_PROTO(struct rxrpc_call *call, enum rxrpc_transmit_trace why), 763 TP_ARGS(call, why), 767 __field(enum rxrpc_transmit_trace, why ) 775 __entry->why = why; 783 __print_symbolic(__entry->why, rxrpc_transmit_traces), [all …]
|
| H A D | fscache.h | 368 enum fscache_page_trace why), 370 TP_ARGS(cookie, page, why), 375 __field(enum fscache_page_trace, why ) 381 __entry->why = why; 386 __print_symbolic(__entry->why, fscache_page_traces), 432 enum fscache_op_trace why), 434 TP_ARGS(cookie, op, why), 439 __field(enum fscache_op_trace, why ) 445 __entry->why = why; 450 __print_symbolic(__entry->why, fscache_op_traces))
|
| /OK3568_Linux_fs/kernel/drivers/infiniband/core/ |
| H A D | uverbs_std_types.c | 43 enum rdma_remove_reason why, in uverbs_free_ah() argument 52 enum rdma_remove_reason why, in uverbs_free_flow() argument 72 enum rdma_remove_reason why, in uverbs_free_mw() argument 79 enum rdma_remove_reason why, in uverbs_free_rwq_ind_tbl() argument 91 if (ib_is_destroy_retryable(ret, why, uobject)) in uverbs_free_rwq_ind_tbl() 103 enum rdma_remove_reason why, in uverbs_free_xrcd() argument 111 ret = ib_destroy_usecnt(&uxrcd->refcnt, why, uobject); in uverbs_free_xrcd() 116 ret = ib_uverbs_dealloc_xrcd(uobject, xrcd, why, attrs); in uverbs_free_xrcd() 123 enum rdma_remove_reason why, in uverbs_free_pd() argument 129 ret = ib_destroy_usecnt(&pd->usecnt, why, uobject); in uverbs_free_pd() [all …]
|
| /OK3568_Linux_fs/external/xserver/os/ |
| H A D | rpcauth.c | 54 static enum auth_stat why; variable 70 why = AUTH_FAILED; /* generic error, since there is no AUTH_BADALLOC */ 82 why = AUTH_FAILED; 99 why = AUTH_TOOWEAK; 103 if ((why = __authenticate(&r, &msg)) != AUTH_OK) { 105 if ((why = _authenticate(&r, &msg)) != AUTH_OK) { 141 "Unable to authenticate secure RPC client (why=%d)", why);
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/arm/gcc-arm-10.3-2021.07-x86_64-arm-none-linux-gnueabihf/share/doc/gdb/ |
| H A D | Rationale.html | 83 <dt><b>Why are you doing everything in LONGEST?</b></dt> 106 <dt><b>Why don’t you have <code>></code> or <code><=</code> operators?</b></dt> 114 <dt><b>Why do you have <code>log_not</code>?</b></dt> 115 <dt><b>Why do you have <code>ext</code>?</b></dt> 116 <dt><b>Why do you have <code>zero_ext</code>?</b></dt> 134 <dt><b>Why not have sign-extending variants of the <code>ref</code> operators?</b></dt> 139 <dt><b>Why not have constant-address variants of the <code>ref</code> operators?</b></dt> 144 <dt><b>Why do the <code>ref<var>n</var></code> operators have to support unaligned fetches?</b></dt> 162 <dt><b>Why are there no side-effecting operators?</b></dt> 169 <dt><b>Why aren’t the <code>goto</code> ops PC-relative?</b></dt> [all …]
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/share/doc/gdb/ |
| H A D | Rationale.html | 83 <dt><b>Why are you doing everything in LONGEST?</b></dt> 106 <dt><b>Why don’t you have <code>></code> or <code><=</code> operators?</b></dt> 114 <dt><b>Why do you have <code>log_not</code>?</b></dt> 115 <dt><b>Why do you have <code>ext</code>?</b></dt> 116 <dt><b>Why do you have <code>zero_ext</code>?</b></dt> 134 <dt><b>Why not have sign-extending variants of the <code>ref</code> operators?</b></dt> 139 <dt><b>Why not have constant-address variants of the <code>ref</code> operators?</b></dt> 144 <dt><b>Why do the <code>ref<var>n</var></code> operators have to support unaligned fetches?</b></dt> 162 <dt><b>Why are there no side-effecting operators?</b></dt> 169 <dt><b>Why aren’t the <code>goto</code> ops PC-relative?</b></dt> [all …]
|
| /OK3568_Linux_fs/yocto/poky/scripts/ |
| H A D | cp-noerror | 40 except EnvironmentError as why: 41 errors.append((srcname, dstname, str(why))) 44 except OSError as why: 45 errors.extend((src, dst, str(why)))
|
| /OK3568_Linux_fs/u-boot/doc/ |
| H A D | feature-removal-schedule.txt | 3 exactly is going away, when it will be gone, why it is being removed, 13 Why: As the 'mtest' command is no longer default, a number of platforms 25 Why: We now have a PHY library, which allows everyone to share PHY 35 Why: Over time, a couple of files have sneaked in into the U-Boot
|
| /OK3568_Linux_fs/buildroot/docs/manual/ |
| H A D | faq-troubleshooting.txt | 29 === Why is there no compiler on the target? 55 === Why are there no development files on the target? 65 === Why is there no documentation on the target? 75 [[faq-why-not-visible-package]] 76 === Why are some packages not visible in the Buildroot config menu? 93 [[faq-why-not-use-target-as-chroot]] 94 === Why not use the target directory as a chroot directory? 111 === Why doesn't Buildroot generate binary packages (.deb, .ipkg...)?
|
| /OK3568_Linux_fs/kernel/fs/afs/ |
| H A D | dir_edit.c | 188 enum afs_edit_dir_reason why) in afs_edit_dir_add() argument 293 trace_afs_edit_dir(vnode, why, afs_edit_dir_create_nospc, 0, 0, 0, 0, name->name); in afs_edit_dir_add() 309 trace_afs_edit_dir(vnode, why, afs_edit_dir_create, b, slot, in afs_edit_dir_add() 344 trace_afs_edit_dir(vnode, why, afs_edit_dir_create_inval, 0, 0, 0, 0, name->name); in afs_edit_dir_add() 353 trace_afs_edit_dir(vnode, why, afs_edit_dir_create_error, 0, 0, 0, 0, name->name); in afs_edit_dir_add() 366 struct qstr *name, enum afs_edit_dir_reason why) in afs_edit_dir_remove() argument 438 trace_afs_edit_dir(vnode, why, afs_edit_dir_delete_noent, in afs_edit_dir_remove() 446 trace_afs_edit_dir(vnode, why, afs_edit_dir_delete, b, slot, in afs_edit_dir_remove() 476 trace_afs_edit_dir(vnode, why, afs_edit_dir_delete_inval, in afs_edit_dir_remove() 487 trace_afs_edit_dir(vnode, why, afs_edit_dir_delete_error, in afs_edit_dir_remove()
|
| /OK3568_Linux_fs/kernel/arch/mips/sgi-ip27/ |
| H A D | TODO | 1 1. Need to figure out why PCI writes to the IOC3 hang, and if it is okay 4 3. Need to figure out why address swaizzling is needed in inw/outw for 10 6. Investigate why things do not work without the setup_test() call
|
| /OK3568_Linux_fs/yocto/meta-openembedded/meta-perl/recipes-perl/libxml/libxml-libxml-perl/ |
| H A D | disable-libxml2-check.patch | 42 -to see the exact reason why the detection of libxml2 installation 43 -failed or why Makefile.PL was not able to compile a test program. 68 +#to see the exact reason why the detection of libxml2 installation 69 +#failed or why Makefile.PL was not able to compile a test program.
|
| /OK3568_Linux_fs/kernel/Documentation/maintainer/ |
| H A D | rebasing-and-merging.rst | 123 merge, say *why* the merge is being done. For a lower-level tree, "why" is 149 Why is that? Back merges will muddy the development history of your own 158 sure to document *why* it was required in the commit message. As always, 190 as always, in such situations, the merge commit should explain why the 226 arisen and be prepared to explain why something abnormal needs to be done.
|
| H A D | pull-requests.rst | 51 so outline what is contained here, why it should be merged, and what, if 60 to understand what I'm pulling, and why I should pull it. I also 71 what they do and why they do it, but explain the _timing_. What 159 description of that tag (which is why you need to provide good
|
| /OK3568_Linux_fs/kernel/Documentation/RCU/ |
| H A D | UP.rst | 52 Why is it *not* legal to invoke synchronize_rcu() in this case? 100 Why can't synchronize_rcu() return immediately on UP systems running 106 Why is it *not* legal to invoke synchronize_rcu() in this case? 136 Why can't synchronize_rcu() return immediately on UP systems
|
| H A D | rcu.rst | 20 - Why would anyone want to use RCU? 51 thing at a time, why should I wait for a grace period? 69 - Why the name "RCU"?
|
| /OK3568_Linux_fs/kernel/Documentation/admin-guide/ |
| H A D | tainted-kernels.rst | 8 cause might be the event that got the kernel tainted. That's why bug reports 14 trustworthy. That's also why the kernel will print the tainted state when it 25 why the kernel was tainted is shown after the Process ID ('PID:') and a shortened 52 tainted; any other number indicates the reasons why it is. The easiest way to 132 there should be other information in the log indicating why this tainting
|
| /OK3568_Linux_fs/kernel/Documentation/ABI/testing/ |
| H A D | sysfs-class-net-statistics | 170 See the driver for the exact reasons as to why the packets were 180 why the packets were dropped. 188 FIFO error. See the driver for the exact reasons as to why the 198 reasons as to why the packets were dropped.
|
| /OK3568_Linux_fs/kernel/Documentation/timers/ |
| H A D | timers-howto.rst | 66 - Why not usleep? 76 - Why not msleep for (1ms - 20ms)? 85 - Why is there no "usleep" / What is a good range?
|
| /OK3568_Linux_fs/buildroot/dl/qt5location/git/src/3rdparty/mapbox-gl-native/deps/boost/1.65.1/include/boost/geometry/algorithms/detail/is_valid/ |
| H A D | interface.hpp | 176 valid or not, and if not valid indicating the reason why 202 valid or not, and if not valid indicating the reason why 226 is valid or not, and if not valid a reason why 253 is valid or not, and if not valid a reason why
|
| /OK3568_Linux_fs/kernel/arch/um/drivers/ |
| H A D | slirp.h | 9 * XXX this next definition is here because I don't understand why this 14 * or why I can't typecast like this:
|
| /OK3568_Linux_fs/kernel/Documentation/bpf/ |
| H A D | bpf_design_QA.rst | 29 Q: Why C calling convention was chosen? 132 For example why BPF_JNE and other compare and jumps are not cpu-like? 137 Q: Why BPF_DIV instruction doesn't map to x64 div? 143 Q: Why there is no BPF_SDIV for signed divide operation? 148 Q: Why BPF has implicit prologue and epilogue? 157 Q: Why BPF_JLT and BPF_JLE instructions were not introduced in the beginning?
|
| /OK3568_Linux_fs/yocto/poky/bitbake/lib/toaster/toastergui/static/jquery-treetable-license/ |
| H A D | README.md | 5 directory structure or a nested list. Why not use a list, you say? Because lists 7 uses tables, doesn't it? Yes. Why do I use a table to display a list? Because I
|
| /OK3568_Linux_fs/kernel/fs/cachefiles/ |
| H A D | namei.c | 86 enum fscache_why_object_killed why) in cachefiles_mark_object_buried() argument 107 trace_cachefiles_mark_buried(NULL, dentry, why); in cachefiles_mark_object_buried() 118 trace_cachefiles_mark_buried(object, dentry, why); in cachefiles_mark_object_buried() 125 if (why != FSCACHE_OBJECT_IS_STALE) in cachefiles_mark_object_buried() 126 fscache_object_mark_killed(&object->fscache, why); in cachefiles_mark_object_buried() 292 enum fscache_why_object_killed why) in cachefiles_bury_object() argument 313 trace_cachefiles_unlink(object, rep, why); in cachefiles_bury_object() 317 cachefiles_mark_object_buried(cache, rep, why); in cachefiles_bury_object() 415 trace_cachefiles_rename(object, rep, grave, why); in cachefiles_bury_object() 423 cachefiles_mark_object_buried(cache, rep, why); in cachefiles_bury_object()
|