[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87a7ur10k3.fsf@concordia.ellerman.id.au>
Date: Fri, 30 Mar 2018 00:19:40 +1100
From: Michael Ellerman <mpe@...erman.id.au>
To: Shea Levy <shea@...alevy.com>, Joe Perches <joe@...ches.com>,
linux-riscv@...ts.infradead.org, linux-kernel@...r.kernel.org
Cc: Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Paul Mackerras <paulus@...ba.org>,
Michal Hocko <mhocko@...e.com>,
Vlastimil Babka <vbabka@...e.cz>,
Andrew Morton <akpm@...ux-foundation.org>,
Dan Williams <dan.j.williams@...el.com>,
Christophe Leroy <christophe.leroy@....fr>,
Oliver O'Halloran <oohall@...il.com>,
linuxppc-dev@...ts.ozlabs.org
Subject: Re: [PATCH v4 14/16] powerpc: Use generic free_initrd_mem.
Shea Levy <shea@...alevy.com> writes:
> Joe Perches <joe@...ches.com> writes:
>
>> On Wed, 2018-03-28 at 16:36 -0400, Shea Levy wrote:
>>> Signed-off-by: Shea Levy <shea@...alevy.com>
>>
>> Most people seem to want some form of commit message
>> and not just your sign-off.
>>
>
> Ah, if the subject is insufficient I can add some more detail.
Yeah please do.
Seeing this patch in isolation, with no change log, I might think it's
safe for me to just apply it.
But that would break the build because I don't have patch 1.
So for starters you need to explain that part, eg something like:
A previous patch in the series added a weak definition of
free_initrd_mem() in init/initramfs.c.
The powerpc implementation is identical, so it can be removed allowing
the generic version to be used.
Then you could also tell me if you did/didn't build/boot test it.
cheers
Powered by blists - more mailing lists