/openbmc/openbmc/meta-phosphor/recipes-extended/pam/libpam/ |
H A D | pwhistory.conf | 2 remember=0
|
/openbmc/phosphor-user-manager/test/ |
H A D | user_mgr_test.cpp | 381 std::string remember; in TEST_F() local 383 getPamModuleConfValue(tempPWHistoryConfigFile, "remember", remember), in TEST_F() 385 EXPECT_EQ(remember, "0"); in TEST_F() 404 std::string remember; in TEST_F() local 406 getPamModuleConfValue(tempPWHistoryConfigFile, "remember", remember), in TEST_F() 408 EXPECT_EQ(remember, "1"); in TEST_F() 450 std::string remember; in TEST_F() local 452 getPamModuleConfValue(tempPWHistoryConfigFile, "remember", remember), in TEST_F() 457 getPamModuleConfValue(tempPWHistoryConfigFile, "remember", remember), in TEST_F()
|
/openbmc/phosphor-bmc-code-mgmt/bmc/test/ |
H A D | README.md | 12 - WHEN RUNNING UTEST remember to take advantage of the gtest capabilities.
|
/openbmc/openpower-pnor-code-mgmt/test/ |
H A D | README.md | 12 - WHEN RUNNING UTEST remember to take advantage of the gtest capabilities.
|
/openbmc/qemu/tests/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/linux/arch/sparc/lib/ |
H A D | clear_page.S | 81 mov %o0, %g1 ! remember vaddr for tlbflush
|
/openbmc/linux/arch/x86/platform/olpc/ |
H A D | xo1-wakeup.S | 97 # This is the stack context we want to remember
|
/openbmc/linux/drivers/net/hippi/ |
H A D | Kconfig | 16 under Linux, say Y here (you must also remember to enable the driver
|
/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/linux/tools/testing/selftests/arm64/fp/ |
H A D | README | 77 can't remember whether my branch is new enough for that. Try without
|
/openbmc/qemu/scripts/coccinelle/ |
H A D | reset-type.cocci | 23 // resettable_class_set_parent_phases, and remember the function name.
|
/openbmc/linux/Documentation/process/ |
H A D | 6.Followthrough.rst | 40 people remember who wrote kernel code, but there is little lasting fame 91 going to remember all the details of the code you posted the last time 218 be hurtful and discouraging, but the community will remember your reaction
|
/openbmc/linux/Documentation/filesystems/ |
H A D | journalling.rst | 46 reenter a transaction if necessary, but remember you must call 74 single outstanding transaction at any one time, remember nothing commits
|
/openbmc/linux/fs/affs/ |
H A D | Changes | 321 - Several other changes I just cannot remember 331 - Lots of things I remember even less ...
|
/openbmc/openbmc/poky/meta/recipes-connectivity/connman/connman-gnome/ |
H A D | connman-gnome-fix-dbus-interface-name.patch | 147 gboolean remember);
|
/openbmc/linux/Documentation/userspace-api/media/v4l/ |
H A D | mmap.rst | 106 buffers[i].length = buffer.length; /* remember for munmap() */ 186 buffers[i].length[j] = buffer.m.planes[j].length; /* remember for munmap() */
|
/openbmc/linux/Documentation/networking/ |
H A D | page_pool.rst | 95 This is important to remember when using fragments (``PP_FLAG_PAGE_FRAG``),
|
/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/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/docs/designs/ |
H A D | design-template.md | 24 However you are free to prototype the implementation, but remember that you
|
/openbmc/qemu/ |
H A D | qemu-img-cmds.hx | 11 HXCOMM When amending the rST sections, please remember to copy the usage
|
/openbmc/linux/Documentation/admin-guide/ |
H A D | svga.rst | 22 remember its mode ID (the four-digit hexadecimal number) and then 148 (remember that mode scanning is not done automatically).
|