Home
last modified time | relevance | path

Searched full:know (Results 1 – 25 of 2345) sorted by relevance

12345678910>>...94

/linux/arch/riscv/
H A DKconfig.errata22 If you don't know what to do here, say "Y".
66 If you don't know what to do here, say "Y".
77 If you don't know what to do here, say "Y".
117 If you don't know what to do here, say "Y".
130 If you don't know what to do here, say "Y".
143 If you don't know what to do here, say "Y".
154 If you don't know what to do here, say "Y".
H A DKconfig.vendor16 If you don't know what to do here, say Y.
29 If you don't know what to do here, say Y.
42 If you don't know what to do here, say Y.
55 If you don't know what to do here, say Y.
68 If you don't know what to do here, say Y.
H A DKconfig450 If you don't know what to do here, say N.
564 If you don't know what to do here, say Y.
594 If you don't know what to do here, say Y.
611 If you don't know what to do here, say Y.
632 If you don't know what to do here, say Y.
643 If you don't know what to do here, say Y.
694 If you don't know what to do here, say Y.
711 If you don't know what to do here, say Y.
746 If you don't know what to do here, say Y.
761 If you don't know what to do here, say Y.
[all …]
/linux/tools/testing/selftests/bpf/progs/
H A Dverifier_var_off.c26 * &skb->pkt_type, but we don't know which \ in variable_offset_ctx_access()
52 * we don't know which \ in stack_read_priv_vs_unpriv()
75 * we don't know which \ in variable_offset_stack_read_uninitialized()
106 * fp-16, but we don't know which \ in stack_write_priv_vs_unpriv()
119 * were in the range of that write (even if the verifier doesn't actually know if
144 * we don't know which \ in stack_write_followed_by_read()
186 * we don't know which. \ in stack_write_clobbers_spilled_regs()
252 * we don't know which \ in access_max_out_of_bound()
310 * we don't know which \ in access_min_out_of_bound()
339 /* Add it to fp. We now have either fp-12 or fp-16, but we don't know\ in access_min_off_min_initialized()
[all...]
/linux/arch/microblaze/
H A DKconfig134 Unless you know what you are doing, say N here.
162 Say N here unless you know what you are doing.
188 Say N here unless you know what you are doing.
202 Say N here unless you know what you are doing.
216 Say N here unless you know what you are doing.
/linux/drivers/vfio/
H A DKconfig14 If you don't know what to do here, say N.
28 If you don't know what to do here, say N.
38 If you don't know what to do here, say Y.
76 If you don't know what to do here, say N.
/linux/Documentation/mm/damon/
H A Ddesign.rst19 To know how user-space can do the configurations and start/stop DAMON, refer to
77 To know how user-space can do the configuration via :ref:`DAMON sysfs interface
168 To know how user-space can set the attributes via :ref:`DAMON sysfs interface
383 To know how user-space can use this feature via :ref:`DAMON sysfs interface
427 To know how user-space can set ``apply_interval`` via :ref:`DAMON sysfs
479 To know how user-space can set the action via :ref:`DAMON sysfs interface
496 To know how user-space can set the access pattern via :ref:`DAMON sysfs
519 To know how user-space can set the basic quotas via :ref:`DAMON sysfs interface
550 To know how user-space can set the prioritization weights via :ref:`DAMON sysfs
588 To know how user-space can set the tuning goal metric, the target value, and/or
[all …]
/linux/Documentation/devicetree/bindings/
H A Dcommon-properties.txt15 know the peripheral always needs to be accessed in big endian (BE) mode.
17 unconditionally (e.g. readl/writel). Use this if you know the
71 by all of its devices. The driver needs to know how many devices the
/linux/Documentation/sound/cards/
H A Dbt87x.rst34 The driver is now stable. However, it doesn't know about many TV cards,
35 and it refuses to load for cards it doesn't know.
45 or not, so that future versions of this driver know about your card.
/linux/Documentation/power/
H A Dswsusp-dmcrypt.rst10 You know how dm-crypt works. If not, visit the following web page:
13 You did read Documentation/admin-guide/initrd.rst and know how an initrd works.
14 You know how to create or how to modify an initrd.
119 Please don't mind the weird loop above, busybox's msh doesn't know
/linux/Documentation/i2c/
H A Dinstantiating-devices.rst6 level. Instead, the software must know which devices are connected on each
113 main chip by the means of an I2C bus. You won't know the number of the I2C
138 A variant of this is when you don't know for sure if an I2C device is
232 In general, the kernel should know which I2C devices are connected and
263 device is not officially supported yet but you know it is compatible.
272 available, and you don't need to know what driver the device needs.
/linux/arch/nios2/
H A DKconfig150 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/sound/soc/bcm/
H A DKconfig21 If you don't know what to do here, say N.
30 If you don't know what to do here, say N
/linux/arch/powerpc/
H A DKconfig528 Select this if you know there does have a hardware FPU on your
683 setting can still be useful to bootwrappers that need to know the
880 want. Only change this if you know what you are doing.
893 Say N here unless you know what you are doing.
1174 Unless you know what you are doing, say N here.
1189 Say N here unless you know what you are doing.
1205 Say N here unless you know what you are doing.
1241 Say N here unless you know what you are doing.
1256 Say N here unless you know what you are doing.
1270 Say N here unless you know what you are doing.
[all …]
/linux/Documentation/process/
H A Dmanagement-style.rst45 manage had better know the details better than you, so if they come to
49 (Corollary:if the people you manage don't know the details better than
56 makes you look like you know what you're doing, so what a kernel manager
118 Remember: they'd better know more about the details than you do, and
229 Then make the developer who really screwed up (if you can find them) know
231 future, but so that they know they owe you one. And, perhaps even more
/linux/tools/usb/usbip/libsrc/
H A Dlist.h14 * sometimes we already know the next/prev entries and we can
37 * This is only for internal list manipulation where we know
67 * This is only for internal list manipulation where we know
/linux/arch/openrisc/
H A DKconfig197 If you don't know what to do here, say N.
206 If you don't know what to do here, say Y.
220 Say N here if you know that your OpenRISC processor has
/linux/drivers/vfio/pci/
H A DKconfig21 If you don't know what to do here, say N.
32 If you don't know what to do here, say N.
/linux/Documentation/networking/
H A Darcnet.rst39 (You know, it might be argued that I'm pushing this point a little too much.
124 You will know the driver is installed properly if you get some ARCnet
162 COM20020 data sheets, and you don't know what the other three options refer
270 you never know what you might need.
278 don't know why the defaults on the Amiga didn't work; write to me if
279 you know more.
318 "normal" Warp Bonus Pack, let me know.
452 to the Internet through freedom. If you didn't know how to do the above,
587 If you don't understand that, you probably don't want to know anyway.
/linux/Documentation/scsi/
H A D53c700.rst37 driver, you need to know three things about the way the chip is wired
44 Optionally, you may also need to know other things, like how to read
69 This will be a standard SCSI driver (I don't know of a good document
/linux/drivers/uio/
H A DKconfig12 If you don't know what to do here, say N.
39 If you don't know what to do here, say N.
56 If you don't know what to do here, say N.
/linux/Documentation/fb/
H A Dmetronomefb.rst30 originally labeled 23P01201_60_WT0107_MTC. I do not know what it stands for.
33 I neither have access to nor know exactly what the waveform does in terms of
/linux/arch/x86/kernel/
H A Di8253.c18 * HPET replaces the PIT, when enabled. So we need to know, which of
29 * requires to know the local APIC timer frequency as it normally is
/linux/drivers/hid/bpf/progs/
H A DWacom__ArtPen.bpf.c22 * - to solve that, given that we know that the next event will be the same as
61 * we need to know which device has which offsets
80 * the verifier to know we are addressing the memory correctly
/linux/drivers/hwtracing/stm/
H A DKconfig41 If you don't know what this is, say N.
49 If you don't know what this is, say N.

12345678910>>...94