| /openbmc/openbmc/meta-phosphor/recipes-extended/pam/libpam/ |
| H A D | pwhistory.conf | 2 remember=0
|
| /openbmc/phosphor-bmc-code-mgmt/bmc/test/ |
| H A D | README.md | 14 - WHEN RUNNING UTEST remember to take advantage of the gtest capabilities.
|
| /openbmc/openpower-pnor-code-mgmt/test/ |
| H A D | README.md | 11 - WHEN RUNNING UTEST remember to take advantage of the gtest capabilities.
|
| /openbmc/qemu/tests/qtest/migration/ |
| H A D | Makefile | 28 * inside tests/migration to update, and then remember to send both
|
| /openbmc/phosphor-event/test/ |
| H A D | README.md | 16 * WHEN RUNNING UTEST remember to take advantage
|
| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | Graphics-Gems | 5 …ebmasters - are to be held responsible. Basically, don't be a jerk, and remember that anything fre…
|
| /openbmc/openbmc/poky/meta/recipes-core/picolibc/ |
| H A D | picolibc_git.bb | 16 # early compiler tests from failing, cant remember why I added it
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-kernel/kernel-selftest/kernel-selftest/ |
| H A D | userfaultfd.patch | 140 + type is the trivial no-state-information type, just remember the seed.
268 + Note: It is important that we also remember the locations of the pointers
|
| /openbmc/qemu/scripts/coccinelle/ |
| H A D | reset-type.cocci | 23 // resettable_class_set_parent_phases, and remember the function name.
|
| /openbmc/openbmc/poky/meta/recipes-connectivity/connman/connman-gnome/ |
| H A D | connman-gnome-fix-dbus-interface-name.patch | 147 gboolean remember);
|
| /openbmc/openbmc/poky/meta/recipes-core/udev/eudev/ |
| H A D | 0001-random-util.c-sync-dev_urandom-implementation-to-sys.patch | 94 - * remember to use the syscall the
|
| /openbmc/docs/designs/ |
| H A D | design-template.md | 24 However you are free to prototype the implementation, but remember that you
|
| /openbmc/u-boot/tools/patman/ |
| H A D | README | 246 keep track of what happened. When you amend a commit, remember
447 to remember what version you are up to, who you sent the last lot of patches
468 not later when you can't remember which patch you changed. You can always
|
| /openbmc/u-boot/board/synopsys/iot_devkit/ |
| H A D | README | 102 so it gets linked to ICCM address 0x2000_0000 (remember eFlash is not
|
| /openbmc/qemu/docs/devel/ |
| H A D | multiple-iothreads.rst | 26 not shared completely. Sometimes it is useful to remember that although they
|
| /openbmc/qemu/docs/system/ |
| H A D | device-url-syntax.rst.inc | 54 remember that '?' is a shell glob character and may need quoting:
|
| /openbmc/qemu/docs/devel/migration/ |
| H A D | compatibility.rst | 504 do that migration to new machine types if we remember to enable that
505 property for pc-7.2. Notice that we need to remember, it is not
|
| /openbmc/u-boot/doc/ |
| H A D | README.unaligned-memory-access.txt | 92 by 4 (remember, we're reading a 4 byte value here).
|
| /openbmc/docs/ |
| H A D | CONTRIBUTING.md | 356 You are expected to respond to all comments. And remember to use the "reply"
360 or abandoned. When you re-work your change, remember to use `git commit --amend`
|
| H A D | rest-api.md | 243 When using '-d' just remember that json requires quoting.
|
| /openbmc/qemu/docs/interop/ |
| H A D | bitmaps.rst | 305 - Persistent enabled bitmaps will remember their ``+recording`` status on
343 - Persistent disabled bitmaps will remember their ``-recording`` status on
704 remember which bitmaps are associated with which backups.
|
| /openbmc/openbmc/poky/documentation/sdk-manual/ |
| H A D | extensible.rst | 309 It is important to remember that building the item from source
|
| /openbmc/phosphor-host-ipmid/docs/ |
| H A D | testing.md | 380 Some things to remember:
|
| /openbmc/openbmc/poky/documentation/contributor-guide/ |
| H A D | submit-changes.rst | 305 letter title. Another possibility, which is easier to remember, is to pass
552 If you want to save time and not be forced to remember the right options to use
|
| /openbmc/openbmc/poky/documentation/test-manual/ |
| H A D | runtime-testing.rst | 449 layer's ``layer.conf`` file as normal). Just remember the following:
|