Home
last modified time | relevance | path

Searched full:doing (Results 1 – 25 of 2431) sorted by relevance

12345678910>>...98

/kernel/linux/linux-5.10/Documentation/driver-api/nvdimm/
Dsecurity.rst71 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:
/kernel/linux/linux-5.10/Documentation/x86/
Dtlb.rst23 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
/kernel/linux/linux-5.10/include/linux/
Dmm_purgeable.h24 * If @mm is NULL, return with doing nothing.
25 * If @total_purg_pages and @pined_purg_pages are both NULL, return with doing nothing.
35 * If @total_purg_pages and @pined_purg_pages are both NULL, return with doing nothing.
Dasync.h82 * context for where to run the function. By doing this we can try to
101 * context for where to run the function. By doing this we can try to
/kernel/linux/linux-5.10/arch/microblaze/
DKconfig141 Unless you know what you are doing, say N here.
178 Say N here unless you know what you are doing.
204 Say N here unless you know what you are doing.
219 Say N here unless you know what you are doing.
/kernel/linux/linux-5.10/Documentation/driver-api/driver-model/
Dporting.rst25 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::
/kernel/linux/linux-5.10/kernel/
Dparams.c117 const char *doing, in parse_one() argument
124 const char *doing, void *arg)) in parse_one()
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
169 const char *doing, void *arg)) in parse_args()
177 pr_debug("doing %s, parsing ARGS: '%s'\n", doing, args); in parse_args()
188 ret = parse_one(param, val, doing, params, num, in parse_args()
192 doing, param); in parse_args()
198 pr_err("%s: Unknown parameter `%s'\n", doing, param); in parse_args()
[all …]
/kernel/linux/linux-5.10/arch/nios2/
DKconfig156 Say N here unless you know what you are doing.
170 Say N here unless you know what you are doing.
182 Say N here unless you know what you are doing.
/kernel/linux/linux-5.10/drivers/net/mdio/
Dmdio-cavium.c51 * doing reads. in cavium_mdiobus_c45_addr()
90 * doing reads. in cavium_mdiobus_read()
135 * doing reads. in cavium_mdiobus_write()
/kernel/linux/linux-5.10/Documentation/core-api/
Dkref.rst146 Don't assume you know what you are doing and use the above construct.
147 First of all, you may not know what you are doing. Second, you may
148 know what you are doing (there are some situations where locking is
150 know what they are doing may change the code or copy the code. It's
234 same lock. Note that doing everything in the release routine is still
/kernel/linux/linux-5.10/arch/powerpc/
DKconfig773 Say N unless you know what you are doing.
793 want. Only change this if you know what you are doing.
806 Say N here unless you know what you are doing.
1002 Say Y unless you know what you are doing and the filter is causing
1109 Unless you know what you are doing, say N here.
1124 Say N here unless you know what you are doing.
1140 Say N here unless you know what you are doing.
1173 Say N here unless you know what you are doing.
1188 Say N here unless you know what you are doing.
1202 Say N here unless you know what you are doing.
[all …]
/kernel/linux/linux-5.10/Documentation/admin-guide/nfs/
Dnfsd-admin-interfaces.rst14 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
/kernel/linux/linux-5.10/Documentation/ABI/testing/
Dprocfs-diskstats22 13 time spent doing I/Os (ms)
23 14 weighted time spent doing I/Os (ms)
Dsysfs-class-fpga-manager34 * write complete = Doing post programming steps
35 * write complete error = Error while doing post programming
/kernel/linux/linux-5.10/Documentation/sh/
Dregister-banks.rst28 registers when doing exception handling).
32 - Used by do_IRQ() and friends for doing irq mapping based off
/kernel/linux/linux-5.10/Documentation/vm/
Dpage_frags.rst21 advantage to doing this is that multiple calls to get_page can be avoided
41 page via a single call. The advantage to doing this is that it allows for
/kernel/linux/linux-5.10/drivers/mtd/spi-nor/controllers/
DKconfig43 Say N here unless you know what you are doing. Overwriting the
60 Say N here unless you know what you are doing. Overwriting the
/kernel/linux/linux-5.10/arch/powerpc/include/asm/
Dxive-regs.h20 * 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
/kernel/linux/linux-5.10/tools/perf/util/
Dpath.c3 * I'm tired of doing "vsnprintf()" etc just to open a
8 * useful for doing things like
/kernel/linux/linux-5.10/arch/openrisc/kernel/
Dunwinder.c40 * 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
/kernel/linux/linux-5.10/arch/powerpc/mm/book3s64/
Dradix_hugetlbpage.c39 * A vairant of hugetlb_get_unmapped_area doing topdown search
80 * We are always doing an topdown search here. Slice code in radix__hugetlb_get_unmapped_area()
/kernel/linux/linux-5.10/drivers/md/bcache/
Dclosure.h18 * progress" - in flight bios, some other thread that's doing something else -
75 * closure - _always_ use continue_at(). Doing so consistently will help
98 * as doing a tail call.
126 * continue_at() and closure_return() clear it for you, if you're doing
/kernel/linux/linux-5.10/Documentation/admin-guide/
Drtc.rst66 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
/kernel/linux/linux-5.10/drivers/gpio/
DTODO55 driver infrastructure for doing simpler MMIO GPIO devices and there was
68 #include <linux/gpio/consumer.h> and stop doing custom parsing of the
73 gpiolib-of.c: in some cases subsystems are doing custom flags and
/kernel/linux/linux-5.10/tools/testing/ktest/examples/include/
Dpatchcheck.conf10 # 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.

12345678910>>...98