Home
last modified time | relevance | path

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

12345678910>>...236

/kernel/linux/linux-6.6/arch/riscv/
DKconfig.errata22 If you don't know what to do here, say "Y".
43 If you don't know what to do here, say "Y".
54 If you don't know what to do here, say "Y".
75 If you don't know what to do here, say "Y".
87 If you don't know what to do here, say "Y".
100 If you don't know what to do here, say "Y".
DKconfig370 If you don't know what to do here, say N.
456 If you don't know what to do here, say Y.
475 If you don't know what to do here, say Y.
493 If you don't know what to do here, say Y.
513 If you don't know what to do here, say Y.
524 If you don't know what to do here, say Y.
548 If you don't know what to do here, say Y.
565 If you don't know what to do here, say Y.
578 If you don't know what to do here, say Y.
622 If you don't know what to do here, say Y.
[all …]
/kernel/linux/linux-5.10/tools/testing/selftests/bpf/verifier/
Dvar_off.c9 * &skb->pkt_type, but we don't know which
31 * we don't know which
53 * we don't know which
74 * we don't know which
82 * that write (even if the verifier doesn't actually know
110 * we don't know which.
176 * we don't know which
201 * we don't know which
225 /* Add it to fp. We now have either fp-12 or fp-16, but we don't know
250 /* Add it to fp. We now have either fp-12 or fp-16, but we don't know
[all …]
/kernel/linux/linux-6.6/tools/testing/selftests/bpf/progs/
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()
281 * we don't know which \ in access_min_out_of_bound()
310 /* 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 …]
/kernel/linux/linux-6.6/drivers/vfio/platform/reset/
DKconfig8 If you don't know what to do here, say N.
15 If you don't know what to do here, say N.
24 If you don't know what to do here, say N.
/kernel/linux/linux-6.6/arch/microblaze/
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.
/kernel/linux/linux-5.10/drivers/vfio/platform/reset/
DKconfig8 If you don't know what to do here, say N.
16 If you don't know what to do here, say N.
25 If you don't know what to do here, say N.
/kernel/linux/linux-6.6/drivers/vfio/
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.
/kernel/linux/linux-6.6/rust/kernel/
Dtask.rs109 // that `TaskRef` is not `Send`, we know it cannot be transferred to another thread in current()
118 // SAFETY: By the type invariant, we know that `self.0` is a valid task. Valid tasks always in group_leader()
123 // and given that a task has a reference to its group leader, we know it must be valid for in group_leader()
130 // SAFETY: By the type invariant, we know that `self.0` is a valid task. Valid tasks always in pid()
137 // SAFETY: By the type invariant, we know that `self.0` is valid. in signal_pending()
143 // SAFETY: By the type invariant, we know that `self.0.get()` is non-null and valid. in wake_up()
/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-6.6/Documentation/filesystems/
Dhpfs.rst95 that if somebody (I don't know who?) has set "UID", "GID", "MODE" or "DEV"
105 chgrp symlinks but I don't know what is it good for. chmoding symlink results
110 extended attributes and partly in OS2SYS.INI. I don't want (and don't know how)
146 should work. If you have OS/2 server, use only read-only mode. I don't know how
148 list, I don't know how to delete them when file is deleted and how to not
180 reasons. If you extremely wish to update them, let me know, I'll write it (but
187 anybody know what does it mean?
201 whole created by this driver, it is BUG - let me know about it.
259 1.93 Modified, so that it works with kernels >= 2.1.131, I don't know if it
/kernel/linux/linux-5.10/Documentation/filesystems/
Dhpfs.rst95 that if somebody (I don't know who?) has set "UID", "GID", "MODE" or "DEV"
105 chgrp symlinks but I don't know what is it good for. chmoding symlink results
110 extended attributes and partly in OS2SYS.INI. I don't want (and don't know how)
146 should work. If you have OS/2 server, use only read-only mode. I don't know how
148 list, I don't know how to delete them when file is deleted and how to not
180 reasons. If you extremely wish to update them, let me know, I'll write it (but
187 anybody know what does it mean?
201 whole created by this driver, it is BUG - let me know about it.
259 1.93 Modified, so that it works with kernels >= 2.1.131, I don't know if it
/kernel/linux/linux-5.10/Documentation/i2c/
Dinstantiating-devices.rst6 level. Instead, the software must know which devices are connected on each
109 main chip by the means of an I2C bus. You won't know the number of the I2C
132 A variant of this is when you don't know for sure if an I2C device is
224 In general, the kernel should know which I2C devices are connected and
255 device is not officially supported yet but you know it is compatible.
264 available, and you don't need to know what driver the device needs.
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/
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
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/
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
/kernel/linux/linux-6.6/Documentation/sound/cards/
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.
/kernel/linux/linux-5.10/Documentation/sound/cards/
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.
/kernel/linux/linux-5.10/arch/powerpc/
DKconfig451 Select this if you know there does have a hardware FPU on your
588 setting can still be useful to bootwrappers that need to know the
773 Say N unless you know what you are doing.
792 want. Only change this if you know what you are doing.
805 Say N here unless you know what you are doing.
1001 Say Y unless you know what you are doing and the filter is causing
1108 Unless you know what you are doing, say N here.
1123 Say N here unless you know what you are doing.
1139 Say N here unless you know what you are doing.
1172 Say N here unless you know what you are doing.
[all …]
/kernel/linux/linux-5.10/drivers/vfio/platform/
DKconfig11 If you don't know what to do here, say N.
21 If you don't know what to do here, say N.
/kernel/linux/linux-6.6/Documentation/power/
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
/kernel/linux/linux-5.10/Documentation/core-api/
Ddma-attributes.rst87 - You know that the accesses to this memory won't thrash the TLB.
88 You might know that the accesses are likely to be sequential or
92 - You know that the penalty of TLB misses while accessing the
96 - You know that the DMA mapping is fairly transitory. If you expect
/kernel/linux/linux-6.6/Documentation/core-api/
Ddma-attributes.rst87 - You know that the accesses to this memory won't thrash the TLB.
88 You might know that the accesses are likely to be sequential or
92 - You know that the penalty of TLB misses while accessing the
96 - You know that the DMA mapping is fairly transitory. If you expect
/kernel/linux/linux-5.10/Documentation/power/
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
/kernel/linux/linux-6.6/arch/nios2/
DKconfig148 Say N here unless you know what you are doing.
162 Say N here unless you know what you are doing.
174 Say N here unless you know what you are doing.
/kernel/linux/linux-6.6/drivers/vfio/platform/
DKconfig17 If you don't know what to do here, say N.
28 If you don't know what to do here, say N.

12345678910>>...236