Home
last modified time | relevance | path

Searched full:knows (Results 1 – 25 of 733) sorted by relevance

12345678910>>...30

/openbmc/openbmc/poky/meta/recipes-support/lzo/lzo/
H A D0001-Use-memcpy-instead-of-reinventing-it.patch6 least in my brief testing with lzop), and knows the alignment
38 + * constant n to be as fast as handwritten code, and knows which architectures
63 + * constant n to be as fast as handwritten code, and knows which architectures
/openbmc/linux/Documentation/RCU/
H A Drcu_dereference.rst28 the section entitled "EXAMPLE WHERE THE COMPILER KNOWS TOO MUCH"
39 The compiler simply knows too much about integral values to
104 Because the compiler now knows that the value of "p" is exactly
119 compiler knows that the pointer is NULL, you had better
189 However, please note that if the compiler knows that the
328 EXAMPLE WHERE THE COMPILER KNOWS TOO MUCH
338 But without rcu_dereference(), the compiler knows more than you might
371 Because the compiler can see all stores to "gp", it knows that the only
/openbmc/linux/arch/powerpc/sysdev/xics/
H A Dics-opal.c161 /* Check if HAL knows about this interrupt */ in ics_opal_check()
175 /* Check if HAL knows about this interrupt */ in ics_opal_mask_unknown()
189 /* Check if HAL knows about this interrupt */ in ics_opal_get_server()
/openbmc/linux/tools/power/cpupower/man/
H A Dcpupower-idle-info.149 time. This state is used if the kernel knows that work has to be processed
69 The intel_idle driver knows the sleep state capabilities of the processor and
/openbmc/openbmc/poky/bitbake/lib/prserv/
H A Dserv.py84 # Check whether the local server already knows the requested configuration.
109 # Ask upstream whether it knows the checksum
124 # Let's ask the upstream server whether it knows it
137 # whether it knows our new output hash
143 # Upstream knows this output hash, let's store it and use it too.
/openbmc/linux/arch/x86/xen/
H A Dxen-asm.S277 * Neither Xen nor the kernel really knows what the old SS and
297 * Neither Xen nor the kernel really knows what the old SS and
319 * Neither Xen nor the kernel really knows what the old SS and
/openbmc/linux/include/crypto/
H A Dsig.h112 * Function invokes the algorithm specific set key function, which knows
128 * Function invokes the algorithm specific set key function, which knows
H A Dakcipher.h96 * function, which knows how to decode and interpret
99 * function, which knows how to decode and interpret
461 * Function invokes the algorithm specific set key function, which knows
483 * Function invokes the algorithm specific set key function, which knows
/openbmc/linux/drivers/gpu/drm/ast/
H A DKconfig12 and a version of AST that knows to fail if KMS
/openbmc/linux/Documentation/process/
H A Dvolatile-considered-harmful.rst40 compiler might think it knows what will be in shared_data, but the
42 forget anything it knows. There will be no optimization problems with
/openbmc/linux/Documentation/driver-api/
H A Dmailbox.rst33 or it can never know (the client knows by way of the protocol).
86 /* The controller already knows async_pkt and sync_pkt */
/openbmc/linux/fs/dlm/
H A DKconfig17 list of resource and locks the local node knows about.
/openbmc/linux/drivers/md/persistent-data/
H A Ddm-transaction-manager.h75 * this operation. Because the tm knows the scope of the transaction it
142 * The superblock location is passed so the metadata space map knows it
/openbmc/openbmc/poky/meta/recipes-graphics/xorg-driver/
H A Dxf86-input-evdev_2.11.0.bb6 devices. It therefore supports all input devices that the kernel knows \
/openbmc/openbmc/meta-openembedded/meta-gnome/recipes-support/libuser/libuser/
H A Dgtkdoc.patch4 This is needed so that gtkdocize as run by autopoint knows where the
/openbmc/linux/Documentation/i2c/
H A Dfunctionality.rst25 I2C_FUNC_PROTOCOL_MANGLING Knows about the I2C_M_IGNORE_NAK,
119 successful, then the driver knows that it can call the following
/openbmc/linux/lib/
H A Dpci_iomap.c140 * CONFIG_GENERIC_IOMAP case, because that's the code that knows about
153 * implement your own pci_iounmap() that knows the rules for where
/openbmc/openbmc/poky/meta/recipes-graphics/xorg-util/util-macros/
H A D0001-xorg-macros.m4.in-do-not-run-AC_CANONICAL_HOST-in-ma.patch9 it against any architeture it knows.
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/websocketpp/websocketpp-0.8.2/
H A D855.patch19 …1.40.0" "1.41.0" "1.42.0" "1.43.0" "1.44.0" "1.46.1") # todo: someone who knows better spesify the…
/openbmc/u-boot/arch/x86/lib/
H A Dcrt0_x86_64_efi.S39 * hand-craft a dummy .reloc section so EFI knows it's a relocatable
H A Dcrt0_ia32_efi.S41 * hand-craft a dummy .reloc section so EFI knows it's a relocatable
/openbmc/linux/arch/powerpc/kernel/
H A Dnote.S14 * Bit 0 indicates that the powerpc kernel binary knows how to run in an
/openbmc/openbmc/poky/meta/recipes-kernel/kexec/kexec-tools/
H A D0002-purgatory-Pass-r-directly-to-linker.patch7 where as gcc knows how to deal with it and passes it down to linker
/openbmc/linux/arch/sparc/prom/
H A Dbootstr_64.c13 /* WARNING: The boot loader knows that these next three variables come one right
/openbmc/linux/Documentation/PCI/
H A Dmsi-howto.rst56 knows that all the data has arrived in memory.
225 lucky, the manufacturer knows this and has indicated it in the ACPI
245 Linux mostly knows about them and automatically enables MSIs if it can.

12345678910>>...30