On 03/07/19 9:00 AM, Oliver O'Halloran wrote:
> On Wed, 2019-06-26 at 02:15 +0530, Hari Bathini wrote:
>> Refactoring fadump code means internal fadump code is referenced from
>> different places. For ease, move internal code to a new file.
> Can you elaborate a bit? I don't really get what the di
On Wed, 2019-06-26 at 02:15 +0530, Hari Bathini wrote:
> Refactoring fadump code means internal fadump code is referenced from
> different places. For ease, move internal code to a new file.
Can you elaborate a bit? I don't really get what the difference between
fadump and fadump-internal code is
On 28/06/19 10:25 AM, Stewart Smith wrote:
> Hari Bathini writes:
>> diff --git a/arch/powerpc/kernel/fadump-common.c
>> b/arch/powerpc/kernel/fadump-common.c
>> new file mode 100644
>> index 000..0182886
>> --- /dev/null
>> +++ b/arch/powerpc/kernel/fadump-common.c
>> @@ -0,0 +1,184 @@
>>
Hari Bathini writes:
> diff --git a/arch/powerpc/kernel/fadump-common.c
> b/arch/powerpc/kernel/fadump-common.c
> new file mode 100644
> index 000..0182886
> --- /dev/null
> +++ b/arch/powerpc/kernel/fadump-common.c
> @@ -0,0 +1,184 @@
> +/*
> + * Firmware-Assisted Dump internal code.
> + *
>
Refactoring fadump code means internal fadump code is referenced from
different places. For ease, move internal code to a new file.
Signed-off-by: Hari Bathini
---
arch/powerpc/include/asm/fadump.h | 112
arch/powerpc/kernel/Makefile|2
arch/powerpc/kernel/fa
