| /openbmc/linux/arch/parisc/math-emu/ |
| H A D | dfcmp.c | 129 * resolve the two possibilities. */ in dbl_fcmp()
156 * resolve the two possibilities. */ in dbl_fcmp()
|
| /openbmc/linux/arch/arm/mach-omap1/ |
| H A D | clock.h | 54 * struct clk.flags possibilities
74 * @flags: see "struct clk.flags possibilities" above
|
| /openbmc/openbmc/meta-arm/meta-arm-bsp/recipes-bsp/trusted-firmware-m/files/corstone1000/ |
| H A D | 0008-Platform-CS1000-Increase-flash-PS-area-size.patch | 9 Increasing the size minimize the possibilities of it to run out
|
| /openbmc/linux/arch/arm/mach-omap2/ |
| H A D | clock.h | 23 /* struct clksel_rate.flags possibilities */
|
| /openbmc/linux/include/linux/platform_data/ |
| H A D | hsmmc-omap.h | 9 * struct omap_hsmmc_dev_attr.flags possibilities
|
| /openbmc/linux/Documentation/devicetree/bindings/mtd/ |
| H A D | nand-chip.yaml | 28 basically three possibilities:
|
| /openbmc/linux/arch/x86/kernel/cpu/ |
| H A D | cpu.h | 9 /* some have two possibilities for cpuid string */
|
| /openbmc/linux/include/linux/ |
| H A D | page-flags-layout.h | 40 * There are five possibilities for how page->flags get laid out. The first
|
| /openbmc/linux/arch/arm64/kernel/ |
| H A D | perf_regs.c | 55 * 32-bit or 64-bit, so we have to cater for both possibilities. in perf_reg_value()
|
| /openbmc/linux/drivers/net/ethernet/mscc/ |
| H A D | ocelot.h | 55 * possibilities of egress port masks for L2 multicast traffic.
|
| /openbmc/linux/include/linux/clk/ |
| H A D | ti.h | 156 * @flags: see "struct clk.flags possibilities" above
181 * struct clk_hw_omap.flags possibilities
|
| /openbmc/openbmc/poky/meta/lib/patchtest/tests/ |
| H A D | test_patch.py | 36 # possibilities: modification to current CVEs, patch directly introduced into the
|
| /openbmc/linux/Documentation/driver-api/media/ |
| H A D | dtv-demux.rst | 38 possibilities of lost update and race condition problems should be
|
| /openbmc/qemu/include/qemu/ |
| H A D | sockets.h | 41 * Any of the possibilities with non-blocking socket's is bad:
|
| /openbmc/qemu/docs/devel/ |
| H A D | s390-cpu-topology.rst | 131 entitlement, giving 6 possibilities for vCPU polarization:
|
| /openbmc/linux/Documentation/block/ |
| H A D | ioprio.rst | 12 scheduling for ages. This document mainly details the current possibilities
|
| /openbmc/linux/drivers/usb/serial/ |
| H A D | aircable.c | 10 * The protocol is very simply, there are two possibilities reading or writing.
|
| /openbmc/linux/Documentation/filesystems/ |
| H A D | fuse.rst | 45 non-privileged mounts. This opens up new possibilities for the use of
160 original request and its INTERRUPT request. There are two possibilities:
|
| /openbmc/linux/drivers/hwmon/ |
| H A D | hs3001.c | 5 * the configuration possibilities, where it needs to be set to 'programming mode'
|
| /openbmc/linux/tools/objtool/ |
| H A D | orc_gen.c | 199 * possibilities (but they shouldn't conflict). in orc_create()
|
| /openbmc/linux/sound/aoa/soundbus/ |
| H A D | soundbus.h | 66 /* supported transfer possibilities, array terminated by
|
| /openbmc/linux/Documentation/driver-api/ |
| H A D | men-chameleon-bus.rst | 34 implementation and does by no means describe the complete possibilities of MCB
|
| /openbmc/linux/drivers/net/wireless/ralink/rt2x00/ |
| H A D | rt2x00crypto.c | 179 * Make room for new data. There are 2 possibilities in rt2x00crypto_rx_insert_iv()
|
| /openbmc/u-boot/include/configs/ |
| H A D | astro_mcf5373l.h | 23 * the possibilities listed below has to be used!
|
| /openbmc/linux/Documentation/RCU/ |
| H A D | rcu_dereference.rst | 148 time ago"? Here are some possibilities:
163 There are many other possibilities involving the Linux
|