Searched full:interesting (Results 1 – 25 of 292) sorted by relevance
12345678910>>...12
| /linux/Documentation/devicetree/bindings/iio/afe/ |
| H A D | voltage-divider.yaml | 14 interesting voltage is often the voltage over the full resistance
49 isn't interesting. In this case, the voltage before the divider
|
| H A D | current-sense-shunt.yaml | 14 the interesting measurement is almost always the current through the
|
| H A D | temperature-sense-rtd.yaml | 18 PT1000, the interesting measurement is almost always the corresponding
|
| H A D | temperature-transducer.yaml | 20 end such as a temperature transducer, the interesting measurement is almost
|
| /linux/kernel/ |
| H A D | Kconfig.preempt | 137 The feature is primarily interesting for Linux distributions which
145 Interesting if you want the same pre-built kernel should be used for
|
| /linux/net/netfilter/ |
| H A D | nf_conntrack_sane.c | 55 /* other fields aren't interesting for conntrack */
104 /* Not an interesting command */ in help()
|
| /linux/arch/m68k/include/asm/ |
| H A D | sun3xprom.h | 17 /* interesting hardware locations */
|
| /linux/arch/mips/include/asm/mach-ip32/ |
| H A D | cpu-feature-overrides.h | 14 * R5000 has an interesting "restriction": ll(d)/sc(d)
|
| /linux/Documentation/admin-guide/hw-vuln/ |
| H A D | l1tf.rst | 194 interesting data to an attacker, but they can leak information about the
232 declared as non-interesting for an attacker without deep inspection of
261 guests, provide interesting data for an attacker depends on the system
263 of the interrupts it can be assumed that they won't expose interesting
432 interesting for an attacker. This still can leak host memory
|
| /linux/Documentation/accounting/ |
| H A D | cgroupstats.rst | 16 statistics on interesting events), should be very easy to add. Currently
|
| /linux/Documentation/admin-guide/device-mapper/ |
| H A D | zero.rst | 11 One very interesting use of dm-zero is for creating "sparse" devices in
|
| /linux/Documentation/ABI/testing/ |
| H A D | pstore | 12 of the console log is captured, but other interesting
|
| /linux/include/linux/ |
| H A D | scx200.h | 9 /* Interesting stuff for the National Semiconductor SCx200 CPU */
|
| H A D | regset.h | 85 * Return %0 if no interesting state in this thread.
86 * Return >%0 number of @size units of interesting state.
|
| /linux/tools/testing/selftests/powerpc/pmu/ebb/ |
| H A D | ebb_on_child_test.c | 18 * Tests we can setup an EBB on our child. Nothing interesting happens, because
|
| /linux/Documentation/i2c/busses/ |
| H A D | i2c-sis630.rst | 21 This can be interesting for chipsets not named
|
| /linux/kernel/kcsan/ |
| H A D | permissive.h | 84 * changed) More often than not, they come with interesting in kcsan_ignore_data_race()
|
| /linux/arch/arm/mach-omap2/ |
| H A D | omap_opp_data.h | 38 * device the kernel boots up on. It is interesting to remember that each IP
|
| /linux/drivers/irqchip/ |
| H A D | irq-aspeed-i2c-ic.c | 47 * Set simple handler and mark IRQ as valid. Nothing interesting to do here
|
| /linux/fs/btrfs/ |
| H A D | Kconfig | 58 interesting to developers.
|
| /linux/tools/power/acpi/ |
| H A D | Makefile.config | 52 # to something more interesting, like "arm-linux-". If you want
|
| /linux/arch/x86/pci/ |
| H A D | intel_mid.c | 7 * Moorestown has an interesting PCI implementation:
306 * Moorestown has an interesting PCI implementation (see above).
|
| /linux/Documentation/driver-api/acpi/ |
| H A D | scan_handlers.rst | 66 interesting to the given scan handler and may be matched against the next scan
|
| /linux/arch/arm/boot/dts/marvell/ |
| H A D | kirkwood-b3.dts | 114 * mix together giving some interesting combinations.
|
| /linux/tools/testing/selftests/bpf/progs/ |
| H A D | test_pkt_access.c | 34 * Which makes it an interesting test for BTF-enabled verifier.
|
12345678910>>...12