9e57b81861
Unlike pam_update() which takes the subject -- PAMMemoryRegion -- as first argument, init_pam() takes it as fifth (!) argument. This makes it quite hard to figure out what an init_pam() invocation actually initializes. By moving the subject to the front this should become clearer. While at it, lower the DeviceState parameter to Object, also communicating more clearly that this parameter is just the owner rather than some (heavy?) dependency. Signed-off-by: Bernhard Beschow <shentey@gmail.com> Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org> Message-Id: <20230213162004.2797-8-shentey@gmail.com> Reviewed-by: Michael S. Tsirkin <mst@redhat.com> Signed-off-by: Michael S. Tsirkin <mst@redhat.com> |
||
|---|---|---|
| .. | ||
| bonito.h | ||
| designware.h | ||
| dino.h | ||
| gpex.h | ||
| grackle.h | ||
| i440fx.h | ||
| ls7a.h | ||
| mv64361.h | ||
| pam.h | ||
| pnv_phb3_regs.h | ||
| pnv_phb3.h | ||
| pnv_phb4_regs.h | ||
| pnv_phb4.h | ||
| ppce500.h | ||
| q35.h | ||
| remote.h | ||
| sabre.h | ||
| spapr.h | ||
| uninorth.h | ||
| xilinx-pcie.h | ||