| /linux/arch/microblaze/ |
| H A D | Kconfig | 135 Unless you know what you are doing, say N here.
163 Say N here unless you know what you are doing.
189 Say N here unless you know what you are doing.
203 Say N here unless you know what you are doing.
217 Say N here unless you know what you are doing.
|
| /linux/Documentation/driver-api/nvdimm/ |
| H A D | security.rst | 71 When doing an update, it is expected that the existing key is removed from
74 keyid when doing the update operation. It is also expected that the new key
98 The command format for doing a secure erase is:
106 The command format for doing an overwrite is:
120 The command format for doing a master update is:
131 The command format for doing a master erase is:
|
| /linux/drivers/net/mdio/ |
| H A D | mdio-cavium.c | 49 * doing reads. in cavium_mdiobus_c45_addr()
77 * doing reads. in cavium_mdiobus_read_c22()
111 * doing reads. in cavium_mdiobus_read_c45()
146 * doing reads. in cavium_mdiobus_write_c22()
184 * doing reads. in cavium_mdiobus_write_c45()
|
| /linux/Documentation/filesystems/bcachefs/ |
| H A D | SubmittingPatches.rst | 19 work? kasan, are you doing locking work? then lockdep; and ktest includes
24 know what you're doing and make sure you're on the right track. Just make sure
80 their filesystem is currently doing. If you're doing a new feature or looking
94 Additionally, we have a lively user community doing excellent QA work, which
|
| H A D | CodingStyle.rst | 63 Good code is code where you can poke around and see what it's doing -
113 what you're doing you'll be amazed at how patient they're happy to be. Users
121 Spend time doing support and helpdesk stuff. Don't just write code - code isn't
160 often go astray - doing something because it seems like it'll be useful often
|
| /linux/Documentation/arch/x86/ |
| H A D | tlb.rst | 23 entire TLB than doing 2^48/PAGE_SIZE individual flushes.
25 be no collateral damage caused by doing the global flush, and
41 You may be doing too many individual invalidations if you see the
61 Essentially, you are balancing the cycles you spend doing invlpg
|
| /linux/Documentation/driver-api/driver-model/ |
| H A D | porting.rst | 25 doing so, they will exported via the sysfs filesystem. sysfs can be
26 mounted by doing::
60 as a module) by doing::
107 the struct to discourage programmers from doing mindless casts
168 with the driver model core by doing::
172 It can later be unregistered by doing::
246 When the driver registers with the bus (e.g. doing pci_register_driver()),
260 core by doing::
|
| /linux/kernel/ |
| H A D | params.c | 119 const char *doing, in parse_one() argument
152 pr_debug("doing %s: %s='%s'\n", doing, param, val); in parse_one()
153 return handle_unknown(param, val, doing, arg); in parse_one()
161 char *parse_args(const char *doing, in parse_args() argument
175 pr_debug("doing %s, parsing ARGS: '%s'\n", doing, args); in parse_args()
186 ret = parse_one(param, val, doing, params, num, in parse_args()
190 doing, param); in parse_args()
196 pr_err("%s: Unknown parameter `%s'\n", doing, param); in parse_args()
200 doing, val ?: "", param); in parse_args()
204 doing, val ?: "", param); in parse_args()
|
| /linux/arch/nios2/ |
| H A D | Kconfig | 150 Say N here unless you know what you are doing.
164 Say N here unless you know what you are doing.
176 Say N here unless you know what you are doing.
|
| /linux/Documentation/admin-guide/nfs/ |
| H A D | nfsd-admin-interfaces.rst | 14 Before doing that, NFSD can be told which sockets to listen on by
22 If nfsd is started without doing any of these, then it will create one
|
| /linux/drivers/thunderbolt/ |
| H A D | Kconfig | 31 Only enable this if you know what you are doing! Never enable
58 are doing. Normal users and distro kernels should say N here.
|
| /linux/arch/powerpc/include/asm/ |
| H A D | xive-regs.h | 20 * When doing an EOI, the Q bit will indicate if the interrupt
28 * Additionally, some ESB pages support doing an EOI via a
29 * store at 0 and some ESBs support doing a trigger via a
|
| /linux/Documentation/arch/sh/ |
| H A D | register-banks.rst | 28 registers when doing exception handling).
32 - Used by do_IRQ() and friends for doing irq mapping based off
|
| /linux/Documentation/ABI/testing/ |
| H A D | procfs-diskstats | 22 13 time spent doing I/Os (ms)
23 14 weighted time spent doing I/Os (ms)
|
| H A D | sysfs-class-fpga-manager | 34 * write complete = Doing post programming steps
35 * write complete error = Error while doing post programming
|
| /linux/Documentation/filesystems/ |
| H A D | directory-locking.rst | 81 from the same NFS4 server and doing lookups in one of them has reached
90 a root of separate tree, it gets attached to the directory we are doing a
118 another filesystem; it may be ecryptfs doing operation in the underlying
119 filesystem, overlayfs doing something to the layers, network filesystem
201 generality we can assume that T1 is the one doing a cross-directory
|
| /linux/Documentation/mm/ |
| H A D | page_frags.rst | 19 advantage to doing this is that multiple calls to get_page can be avoided
39 page via a single call. The advantage to doing this is that it allows for
|
| /linux/tools/testing/selftests/arm64/abi/ |
| H A D | syscall-abi-asm.S | 83 // Set SVCR if we're doing SME
126 // Load FPRs if we're not doing neither SVE nor streaming SVE
152 // Load the SVE registers if we're doing SVE/SME
257 // Save SVCR if we're doing SME
355 // Clear SVCR if we were doing SME so future tests don't have ZA
|
| /linux/arch/openrisc/kernel/ |
| H A D | unwinder.c | 40 * Create a stack trace doing scanning which is frame pointer aware. We can
90 * Create a stack trace by doing a simple scan treating all text addresses
|
| /linux/tools/include/uapi/ |
| H A D | README | 39 So its important not to touch the copies in tools/ when doing changes in
54 What we are doing now is a third option:
|
| /linux/tools/perf/pmu-events/arch/x86/jaketown/ |
| H A D | uncore-memory.json | 184 …E ON mode at one time, the counter will ONLY increment by one rather than doing accumulation. Mul…
194 …E ON mode at one time, the counter will ONLY increment by one rather than doing accumulation. Mul…
204 …E ON mode at one time, the counter will ONLY increment by one rather than doing accumulation. Mul…
214 …E ON mode at one time, the counter will ONLY increment by one rather than doing accumulation. Mul…
224 …E ON mode at one time, the counter will ONLY increment by one rather than doing accumulation. Mul…
234 …E ON mode at one time, the counter will ONLY increment by one rather than doing accumulation. Mul…
244 …E ON mode at one time, the counter will ONLY increment by one rather than doing accumulation. Mul…
254 …E ON mode at one time, the counter will ONLY increment by one rather than doing accumulation. Mul…
|
| /linux/Documentation/admin-guide/ |
| H A D | rtc.rst | 66 A user process can monitor these interrupts by doing a read(2) or a
91 the process of doing this, the kernel briefly turns off RTC periodic
92 interrupts, so be aware of this if you are doing serious work. If you
|
| /linux/drivers/gpio/ |
| H A D | TODO | 64 driver infrastructure for doing simpler MMIO GPIO devices and there was
72 #include <linux/gpio/consumer.h> and stop doing custom parsing of the
77 gpiolib-of.c: in some cases subsystems are doing custom flags and
226 enable GPIOs to the regulator core. Rather than doing that however, we should
|
| /linux/tools/testing/ktest/examples/include/ |
| H A D | patchcheck.conf | 10 # to end with (inclusive). This is similar to doing a git rebase -i PATCH_START~1
11 # and then testing each commit and doing a git rebase --continue.
|
| /linux/tools/testing/selftests/mm/ |
| H A D | protection_keys.c | 668 dprintf1("doing %s(size=%ld, prot=0x%x, pkey=%d)\n", __func__, in malloc_pkey_with_mprotect()
687 dprintf1("doing %s(size=%ld, prot=0x%x, pkey=%d)\n", __func__, in malloc_pkey_anon_huge()
771 dprintf1("doing %s(%ld, %x, %x)\n", __func__, size, prot, pkey); in malloc_pkey_hugetlb()
950 dprintf1("disabling write access to PKEY[1], doing read\n"); in test_read_of_write_disabled_region()
960 dprintf1("disabling access to PKEY[%02d], doing read @ %p\n", pkey, ptr); in test_read_of_access_disabled_region()
973 dprintf1("disabling access to PKEY[%02d], doing read @ %p\n", in test_read_of_access_disabled_region_with_page_already_mapped()
990 "to PKEY[%02d], doing write\n", pkey); in test_write_of_write_disabled_region_with_page_already_mapped()
998 dprintf1("disabling write access to PKEY[%02d], doing write\n", pkey); in test_write_of_write_disabled_region()
1005 dprintf1("disabling access to PKEY[%02d], doing write\n", pkey); in test_write_of_access_disabled_region()
1016 " to PKEY[%02d], doing write\n", pkey); in test_write_of_access_disabled_region_with_page_already_mapped()
[all …]
|