Searched refs:planned (Results 1 – 9 of 9) sorted by relevance
399 int planned; in flash_sect_erase() local403 s_first, s_last, &planned ); in flash_sect_erase()405 if (planned && (rcode == 0)) { in flash_sect_erase()595 int planned; in flash_sect_protect() local598 rcode = flash_fill_sect_ranges( addr_first, addr_last, s_first, s_last, &planned ); in flash_sect_protect()602 if (planned && (rcode == 0)) { in flash_sect_protect()
17 planned new `phosphor-chassis-power` application. This disclaimer will be
13 documented internally, but are planned for direct inclusion into the Linux on
11 `phosphor-chassis-state-manager` application and the planned new
36 that is planned to have PCIE-PCI bridge hot-plugged in.
236 planned for the method to list the isolated units in the redfish since that is
171 data planned for output through reserved-memory. Using reserved-memory for
64 planned to be "consumed" by other nodes must match QEMU
1945 If everything worked as planned, you should see something like this