just (full) in projects: linux - OpenGrok search results

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched full:just (Results 1 – 25 of 4062) sorted by relevance

12 3 4 5 6 7 8 9 10 >>...163

/linux/Documentation/process/
H A D	management-style.rst	62 can be made small by just always making sure that if you were wrong (and 70 Thus the key to avoiding big decisions becomes to just avoiding to do 73 is just pitiful. 80 back-tracking is very easy: just tell everybody that you were an 94 too, and while the actual work was easy enough to undo by just 100 Happily, both of these reasons can be mitigated effectively by just 108 Then, when it really does turn out to be stupid, people just roll their 123 Btw, another way to avoid a decision is to plaintively just whine "can't 124 we just do both?" and look pitiful. Trust me, it works. If it's not 127 situation that they just give up. [all …]
/linux/scripts/
H A D	extract-module-sig.pl	`11 # -d: Just the descriptor values as a sequence of numbers 12 # -n: Just the signer's name 13 # -k: Just the key ID 14 # -s: Just the crypto signature or PKCS#7 message 120 # Just the descriptor values as a sequence of numbers 123 # Just the signer's name 129 # Just the key identifier 135 # Just the crypto signature or PKCS#7 message`
/linux/tools/testing/selftests/bpf/prog_tests/
H A D	arena_atomics.c	11 /* No need to attach it, just run it directly / in test_add() 36 / No need to attach it, just run it directly / in test_sub() 61 / No need to attach it, just run it directly / in test_and() 78 / No need to attach it, just run it directly / in test_or() 95 / No need to attach it, just run it directly / in test_xor() 112 / No need to attach it, just run it directly / in test_cmpxchg() 134 / No need to attach it, just run it directly / in test_xchg() 154 / No need to attach it, just run it directly / in test_uaf() 177 / No need to attach it, just run it directly / in test_arena_atomics() 207 / No need to attach it, just ru [all...]
H A D	atomics.c	`12 /* No need to attach it, just run it directly / in test_add() 37 / No need to attach it, just run it directly / in test_sub() 62 / No need to attach it, just run it directly / in test_and() 84 / No need to attach it, just run it directly / in test_or() 106 / No need to attach it, just run it directly / in test_xor() 128 / No need to attach it, just run it directly / in test_cmpxchg() 150 / No need to attach it, just run it directly */ in test_xchg()`
/linux/lib/kunit/
H A D	executor_test.c	20 /* .run_case is not important, just needs to be non-NULL / 61 / Validate we just have suite2 / in filter_suites_test() 81 / Want: suite1, suite2, NULL -> suite2 (just test1), NULL / in filter_suites_test_glob_test() 87 / Validate we just have suite2 / in filter_suites_test_glob_test() 92 / Now validate we just have test2 / in filter_suites_test_glob_test() 112 free_suite_set_at_end(test, &got); / just in case / in filter_suites_to_empty_test() 143 / .run_case is not important, just needs to be non-NULL / 177 / Validate we just have normal_suite / in filter_attr_test() 182 / Now validate we just have normal test case / in filter_attr_test() 203 free_suite_set_at_end(test, &got); / just in case */ in filter_attr_empty_test()
/linux/Documentation/userspace-api/media/rc/
H A D	lirc-get-features.rst	`45 Unused. Kept just to avoid breaking uAPI. 51 Unused. Kept just to avoid breaking uAPI. 68 Unused. Kept just to avoid breaking uAPI. 144 Unused. Kept just to avoid breaking uAPI. 160 Unused. Kept just to avoid breaking uAPI. 167 Unused. Kept just to avoid breaking uAPI.`
/linux/Documentation/mm/
H A D	active_mm.rst	`25 > discussed on the mailing lists---I just returned from vacation and 33 anonymous address space we just leave the previous address space 74 more. "init_mm" should be considered just a "lazy context when no other 75 context is available", and in fact it is mainly used just at bootup when 80 should generally just do 88 Anyway, I put a pre-patch-2.3.13-1 on ftp.kernel.org just a moment ago,`
/linux/Documentation/admin-guide/
H A D	cputopology.rst	`46 7) topology_sibling_cpumask: just the given CPU 47 8) topology_core_cpumask: just the given CPU 48 9) topology_cluster_cpumask: just the given CPU 49 10) topology_die_cpumask: just the given CPU 50 11) topology_book_cpumask: just the given CPU 51 12) topology_drawer_cpumask: just the given CPU`
/linux/drivers/clk/
H A D	clk_kunit_helpers.c	`58 * Just like clk_get(), except the clk is managed by the test case and is 80 * Just like of_clk_get(), except the clk is managed by the test case and is 102 * Just like clk_hw_get_clk(), except the clk is managed by the test case and 124 * Just like 165 * Just like clk_hw_register(), except the clk registration is managed by the 188 * Just like of_clk_hw_register(), except the clk registration is managed by 216 * Just like of_clk_add_hw_provider(), except the clk_hw provider is managed by`
/linux/tools/perf/pmu-events/arch/x86/pantherlake/
H A D	memory.json	38 …pletion is greater than 1024 cycles. Reported latency may be longer than just the memory latency.… 51 …mpletion is greater than 128 cycles. Reported latency may be longer than just the memory latency.… 64 …ompletion is greater than 16 cycles. Reported latency may be longer than just the memory latency.… 77 …pletion is greater than 2048 cycles. Reported latency may be longer than just the memory latency.… 90 …mpletion is greater than 256 cycles. Reported latency may be longer than just the memory latency.… 103 …ompletion is greater than 32 cycles. Reported latency may be longer than just the memory latency.… 116 …completion is greater than 4 cycles. Reported latency may be longer than just the memory latency.… 129 …mpletion is greater than 512 cycles. Reported latency may be longer than just the memory latency.… 142 …ompletion is greater than 64 cycles. Reported latency may be longer than just the memory latency.… 155 …completion is greater than 8 cycles. Reported latency may be longer than just the memory latency.…
/linux/tools/perf/pmu-events/arch/x86/tigerlake/
H A D	memory.json	28 "PublicDescription": "Counts randomly selected loads when the latency from first dispatch to completion is greater than 128 cycles. Reported latency may be longer than just the memory latency.", 40 "PublicDescription": "Counts randomly selected loads when the latency from first dispatch to completion is greater than 16 cycles. Reported latency may be longer than just the memory latency.", 52 "PublicDescription": "Counts randomly selected loads when the latency from first dispatch to completion is greater than 256 cycles. Reported latency may be longer than just the memory latency.", 64 "PublicDescription": "Counts randomly selected loads when the latency from first dispatch to completion is greater than 32 cycles. Reported latency may be longer than just the memory latency.", 76 "PublicDescription": "Counts randomly selected loads when the latency from first dispatch to completion is greater than 4 cycles. Reported latency may be longer than just the memory latency.", 88 "PublicDescription": "Counts randomly selected loads when the latency from first dispatch to completion is greater than 512 cycles. Reported latency may be longer than just the memory latency.", 100 "PublicDescription": "Counts randomly selected loads when the latency from first dispatch to completion is greater than 64 cycles. Reported latency may be longer than just the memory latency.", 112 "PublicDescription": "Counts randomly selected loads when the latency from first dispatch to completion is greater than 8 cycles. Reported latency may be longer than just the memory latency.",
/linux/scripts/coccinelle/misc/
H A D	warn.cocci	`35 cocci.print_main("printk + WARN_ON can be just WARN",p) 41 msg = "SUGGESTION: printk + WARN_ON can be just WARN" 84 cocci.print_main("printk + WARN_ON_ONCE can be just WARN_ONCE",p) 90 msg = "SUGGESTION: printk + WARN_ON_ONCE can be just WARN_ONCE"`
/linux/arch/xtensa/lib/
H A D	strnlen_user.S	`101 # NOTE that in several places below, we point to the byte just after 107 addi a4, a4, 1 # point just beyond zero byte 111 addi a4, a4, 1+1 # point just beyond zero byte 115 addi a4, a4, 2+1 # point just beyond zero byte 131 addi a4, a4, 3+1 # point just beyond zero byte`
/linux/tools/perf/pmu-events/arch/x86/arrowlake/
H A D	memory.json	166 …pletion is greater than 1024 cycles. Reported latency may be longer than just the memory latency.… 179 …mpletion is greater than 128 cycles. Reported latency may be longer than just the memory latency.… 192 …ompletion is greater than 16 cycles. Reported latency may be longer than just the memory latency.… 205 …pletion is greater than 2048 cycles. Reported latency may be longer than just the memory latency.… 218 …mpletion is greater than 256 cycles. Reported latency may be longer than just the memory latency.… 231 …ompletion is greater than 32 cycles. Reported latency may be longer than just the memory latency.… 244 …completion is greater than 4 cycles. Reported latency may be longer than just the memory latency.… 257 …mpletion is greater than 512 cycles. Reported latency may be longer than just the memory latency.… 270 …ompletion is greater than 64 cycles. Reported latency may be longer than just the memory latency.… 283 …completion is greater than 8 cycles. Reported latency may be longer than just the memory latency.…
/linux/fs/pstore/
H A D	Kconfig	`10 provide the data, so you probably should just go say "Y" 139 This just sets size of kmsg dump (oops, panic, etc) log for 163 This just sets size of pmsg (pmsg_size) for pstore/blk. The size is 175 This just sets size of console log (console_size) to store via 187 This just sets size of ftrace log (ftrace_size) for pstore/blk. The`
/linux/tools/testing/ktest/examples/include/
H A D	patchcheck.conf	`41 # run some test scripts. If you just want to boot test your patches 56 # Instead of just checking for warnings to files that are changed 85 # Note, do not change this option. Just define PATCH_START1 in the 87 # otherwise it will just use PATCH_START if PATCH_START1 is not defined.`
/linux/drivers/gpu/drm/msm/
H A D	NOTES	`30 (Second part is not implemented yet. So far this is just basic KMS 58 register interface is same, just different bases.) 67 Each connector probably ends up being a separate device, just for the 69 have a better way than just stashing the platform device in a global`
/linux/Documentation/dev-tools/
H A D	sparse.rst	`35 ends up looking just like integers to gcc. 37 Quite frankly, you don't need the enum there. The above all really just 40 So the simpler way is to just do:: 86 Once you have it, just do::`
/linux/arch/arm64/kvm/
H A D	fpsimd.c	`21 * Here, we just set the correct metadata to indicate that the FPSIMD 46 * Called just before entering the guest once we are no longer preemptible 59 * Called just after exiting the guest. If the guest FPSIMD state 74 * always 0 and we just need a variable to point to. in kvm_arch_vcpu_ctxsync_fp()`
/linux/tools/perf/pmu-events/arch/x86/meteorlake/
H A D	memory.json	146 …pletion is greater than 1024 cycles. Reported latency may be longer than just the memory latency.… 159 …mpletion is greater than 128 cycles. Reported latency may be longer than just the memory latency.… 172 …ompletion is greater than 16 cycles. Reported latency may be longer than just the memory latency.… 185 …pletion is greater than 2048 cycles. Reported latency may be longer than just the memory latency.… 198 …mpletion is greater than 256 cycles. Reported latency may be longer than just the memory latency.… 211 …ompletion is greater than 32 cycles. Reported latency may be longer than just the memory latency.… 224 …completion is greater than 4 cycles. Reported latency may be longer than just the memory latency.… 237 …mpletion is greater than 512 cycles. Reported latency may be longer than just the memory latency.… 250 …ompletion is greater than 64 cycles. Reported latency may be longer than just the memory latency.… 263 …completion is greater than 8 cycles. Reported latency may be longer than just the memory latency.…
/linux/tools/testing/ktest/
H A D	sample.conf	180 # a file is processed just like the contents of the file was cut and pasted 280 # just like you can config variables. 479 # just define all default options before the first TEST_START 568 # If for some reason you just want to boot the kernel and you do not 569 # want the test to install anything new. For example, you may just want 653 # after the install, where this one runs just before a reboot. 704 # Sometimes there's options that just break the boot and 808 # not want the test to fail just because the system was in 876 # Note, POWERCYCLE_AFTER_REBOOT = 0 does NOT disable it. It just 885 # Note, POWEROFF_AFTER_HALT = 0 does NOT disable it. It just [all …]
/linux/tools/perf/pmu-events/arch/x86/lunarlake/
H A D	memory.json	166 …pletion is greater than 1024 cycles. Reported latency may be longer than just the memory latency.… 179 …mpletion is greater than 128 cycles. Reported latency may be longer than just the memory latency.… 192 …ompletion is greater than 16 cycles. Reported latency may be longer than just the memory latency.… 205 …pletion is greater than 2048 cycles. Reported latency may be longer than just the memory latency.… 218 …mpletion is greater than 256 cycles. Reported latency may be longer than just the memory latency.… 231 …ompletion is greater than 32 cycles. Reported latency may be longer than just the memory latency.… 244 …completion is greater than 4 cycles. Reported latency may be longer than just the memory latency.… 257 …mpletion is greater than 512 cycles. Reported latency may be longer than just the memory latency.… 270 …ompletion is greater than 64 cycles. Reported latency may be longer than just the memory latency.… 283 …completion is greater than 8 cycles. Reported latency may be longer than just the memory latency.…
/linux/rust/kernel/net/phy/
H A D	reg.rs	108 // So it's just an FFI call, open code of `phy_read()` with a valid `phy_device` pointer in read() 120 // So it's just an FFI call, open code of `phy_write()` with a valid `phy_device` pointer in write() 130 // So it's just an FFI call. in read_status() 200 // So it's just an FFI call. in read() 210 // So it's just an FFI call. in write() 219 // So it's just an FFI call. in read_status()
/linux/drivers/spi/
H A D	spi-test.h	`89 #define FILL_MEMSET_8 0 /* just memset with 8 bit / 90 #define FILL_MEMSET_16 1 / just memset with 16 bit / 91 #define FILL_MEMSET_24 2 / just memset with 24 bit / 92 #define FILL_MEMSET_32 3 / just memset with 32 bit */`
/linux/Documentation/filesystems/
H A D	porting.rst	142 FS_LITTER is gone - just remove it from fs_flags. 149 went in - and hadn't been documented ;-/). Just remove it from fs_flags 208 just takes the superblock and inode number as arguments and does the 264 FS_NOMOUNT is gone. If you use it - just set SB_NOUSER in flags 403 initialize the former in inode_init_always(), so just leave it alone in 451 ->get_sb() is gone. Switch to use of ->mount(). Typically it's just 453 the function type. If you were doing it manually, just switch from setting 512 ->lookup() do not take struct nameidata anymore; just the flags. 597 for embedded ("fast") symlinks just set inode->i_link to wherever the 648 ->put_link() is gone - just give the destructor to set_delayed_call() [all …]

12 3 4 5 6 7 8 9 10 >>...163