/openbmc/boost-dbus/include/dbus/impl/ |
H A D | message_iterator.ipp | 20 // returns false if not enough memory- throw bad_alloc 25 // returns false if not enough memory- throw bad_alloc 31 // returns false if not enough memory- throw bad_alloc 42 // returns false if not enough memory- throw bad_alloc
|
/openbmc/openbmc/meta-openembedded/meta-networking/recipes-connectivity/rdist/rdist-6.1.5/ |
H A D | rdist-6.1.5-stat64.patch | 73 - "%s: Not enough free space on filesystem: min %d free %d", 74 + "%s: Not enough free space on filesystem: min %lld free %lld", 81 - "%s: Not enough free files on filesystem: min %d free %d", 82 + "%s: Not enough free files on filesystem: min %lld free %lld",
|
/openbmc/u-boot/drivers/mtd/ubi/ |
H A D | fastmap-wl.c | 122 int enough; in ubi_refill_pools() local 133 enough = 0; in ubi_refill_pools() 145 enough++; in ubi_refill_pools() 160 enough++; in ubi_refill_pools() 162 if (enough == 2) in ubi_refill_pools()
|
/openbmc/linux/drivers/mtd/ubi/ |
H A D | fastmap-wl.c | 136 int enough; in ubi_refill_pools() local 160 enough = 0; in ubi_refill_pools() 172 enough++; in ubi_refill_pools() 186 enough++; in ubi_refill_pools() 188 if (enough == 2) in ubi_refill_pools()
|
/openbmc/linux/Documentation/fb/ |
H A D | sa1100fb.rst | 18 on the kernel command line should be enough to configure the 27 options may not be enough to configure the display. Adding sections to
|
/openbmc/openbmc/meta-openembedded/meta-filesystems/recipes-filesystems/zfs/zfs/ |
H A D | aaf28a4630af60496c9d33db1d06a7d7d8983422.patch | 8 …n_common.h:549:24: error: the register specified for 'w7' is not general enough to be used as a re… 17 …n_common.h:551:24: error: the register specified for 'w8' is not general enough to be used as a re… 26 …n_common.h:552:24: error: the register specified for 'w9' is not general enough to be used as a re…
|
/openbmc/linux/Documentation/mm/damon/ |
H A D | index.rst | 11 - *accurate* (the monitoring output is useful enough for DRAM level memory 13 - *light-weight* (the monitoring overhead is low enough to be applied online),
|
/openbmc/docs/security/ |
H A D | obmc-github-security-advisory-template.md | 41 enough details to differentiate this from similar problems, but not enough
|
/openbmc/linux/Documentation/userspace-api/media/v4l/ |
H A D | vidioc-subdev-g-routing.rst | 56 provided ``num_routes`` is not big enough to contain all the available routes 58 value of the ``num_routes`` field. Application should then reserve enough memory 139 The application provided ``num_routes`` is not big enough to contain
|
/openbmc/openbmc/meta-openembedded/meta-multimedia/recipes-multimedia/dvb-apps/files/dvb-scan-table/dvb-c/ |
H A D | br-Net-Digital | 2 # Just the initial transponder is enough
|
/openbmc/linux/Documentation/arch/arm64/ |
H A D | memory.rst | 126 spaces, the VMEMMAP must be sized large enough for 52-bit VAs and 127 also must be sized large enough to accommodate a fixed PAGE_OFFSET. 141 sized large enough or that addresses are positioned close enough for
|
/openbmc/openbmc/poky/meta/recipes-support/gmp/gmp/ |
H A D | use-includedir.patch | 11 # but anyone knowledgeable enough to be playing with exec_prefix will be able
|
/openbmc/openbmc/meta-raspberrypi/dynamic-layers/multimedia-layer/recipes-multimedia/rpidistro-vlc/files/ |
H A D | 0005-mmal_exit_fix.patch | 13 +// This doesn't seem to be strong enough to reliably kill us if we fail to exit
|
/openbmc/linux/Documentation/watchdog/ |
H A D | watchdog-pm.rst | 18 userspace enough time to resume. [1] [2]
|
/openbmc/u-boot/doc/ |
H A D | README.fdt-overlays | 76 overlay. Make sure you have enough space to grow the base tree without 91 4. Grow it enough so it can 'fit' all the applied overlays
|
/openbmc/linux/Documentation/userspace-api/media/dvb/ |
H A D | dvb-frontend-parameters.rst | 14 data, the structure size weren't enough to fit, and just extending its 18 ioctl's. The new API is flexible enough to add new parameters to
|
/openbmc/linux/Documentation/driver-api/gpio/ |
H A D | using-gpio.rst | 17 in the upstream Linux kernel when you feel it is mature enough and you will get 29 because of not being reusable or abstract enough, or involving a lot of non
|
/openbmc/linux/drivers/staging/olpc_dcon/ |
H A D | TODO | 9 - see if vx855 gpio API can be made similar enough to cs5535 so we can
|
/openbmc/linux/tools/memory-model/litmus-tests/ |
H A D | LB+fencembonceonce+ctrlonceonce.litmus | 9 * combination of a control dependency and a full memory barrier are enough
|
/openbmc/openbmc/poky/meta/recipes-core/ell/ |
H A D | ell_0.71.bb | 7 and compact enough for use on embedded Linux platforms, it is not \
|
/openbmc/linux/Documentation/userspace-api/media/mediactl/ |
H A D | media-ioc-enum-links.rst | 43 with information about the entity's pads. The array must have enough 49 enough room to store all the entity's outbound links. The number of
|
/openbmc/linux/Documentation/userspace-api/media/rc/ |
H A D | lirc-get-features.rst | 61 as long as the kernel is recent enough. Use the 153 transmit, as long as the kernel is recent enough. Use the
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/byacc/byacc/ |
H A D | byacc-open.patch | 2 pass enough arguments to open():
|
/openbmc/linux/Documentation/scheduler/ |
H A D | sched-nice-design.rst | 83 nice levels were not 'punchy enough', so lots of people had to resort to 91 enough), the scheduler was decoupled from 'time slice' and HZ concepts 108 The third complaint (of negative nice levels not being "punchy" enough
|
/openbmc/linux/Documentation/devicetree/bindings/fsi/ |
H A D | fsi-master-gpio.txt | 16 GPIO block is running at a low enough
|