> > Signed-off-by: Sai Praneeth Prakhya <[email protected]> > > Suggested-by: Ard Biesheuvel <[email protected]> > > Cc: Lee Chun-Yi <[email protected]> > > Cc: Dave Young <[email protected]> > > Cc: Borislav Petkov <[email protected]> > > Cc: Laszlo Ersek <[email protected]> > > Cc: Jan Kiszka <[email protected]> > > Cc: Dave Hansen <[email protected]> > > Cc: Bhupesh Sharma <[email protected]> > > Cc: Nicolai Stange <[email protected]> > > Cc: Naresh Bhat <[email protected]> > > Cc: Ricardo Neri <[email protected]> > > Cc: Peter Zijlstra <[email protected]> > > Cc: Taku Izumi <[email protected]> > > Cc: Ravi Shankar <[email protected]> > > Cc: Matt Fleming <[email protected]> > > Cc: Dan Williams <[email protected]> > > Cc: Ard Biesheuvel <[email protected]> > > Do you really think you should cc all these people? >
Sorry! I get that.. > > --- > > drivers/firmware/efi/memmap.c | 28 ++++++++++++++++++++++++++++ > > include/linux/efi.h | 8 ++++++++ > > 2 files changed, 36 insertions(+) > > [snip] > I am now thinking we should perhaps hide the allocation type from the callers > rather than passing around implementation details of the allocator, and have > explicit alloc/free operations. > > Could we instead have a single 'efi_realloc_memmap()' function that takes care > of all of this? Sure! I will give it a try. Regards, Sai
