mbox series

[v3,0/4] initrd: Use unified initrd reserve function in ARM/RISCV

Message ID 20210115054606.124502-1-wangkefeng.wang@huawei.com (mailing list archive)
Headers show
Series initrd: Use unified initrd reserve function in ARM/RISCV | expand

Message

Kefeng Wang Jan. 15, 2021, 5:46 a.m. UTC
Use the same implementation of initrd reserve to avoid duplication.

v3:
- split into four patches, suggested-by Palmer Dabbelt
v2:
- fix build error found by kernel test robot

Kefeng Wang (4):
  initrd: Add the preprocessor guard in initrd.h
  initramfs: Provide a common initrd reserve function
  ARM: Covert to reserve_initrd_mem()
  riscv: Covert to reserve_initrd_mem()

 arch/arm/mm/init.c     | 43 +--------------------------------
 arch/riscv/mm/init.c   | 54 +-----------------------------------------
 include/linux/initrd.h | 11 +++++++++
 init/initramfs.c       | 45 +++++++++++++++++++++++++++++++++++
 4 files changed, 58 insertions(+), 95 deletions(-)

Comments

Kefeng Wang Jan. 17, 2021, 4:57 a.m. UTC | #1
Correct Russell's mail address (from linux@armlinux.org.uk to 
rmk+kernel@armlinux.org.uk, should update the MAINTAINERS)

On 2021/1/15 13:46, Kefeng Wang wrote:
> Use the same implementation of initrd reserve to avoid duplication.
>
> v3:
> - split into four patches, suggested-by Palmer Dabbelt
> v2:
> - fix build error found by kernel test robot
>
> Kefeng Wang (4):
>    initrd: Add the preprocessor guard in initrd.h
>    initramfs: Provide a common initrd reserve function
>    ARM: Covert to reserve_initrd_mem()
>    riscv: Covert to reserve_initrd_mem()
>
>   arch/arm/mm/init.c     | 43 +--------------------------------
>   arch/riscv/mm/init.c   | 54 +-----------------------------------------
>   include/linux/initrd.h | 11 +++++++++
>   init/initramfs.c       | 45 +++++++++++++++++++++++++++++++++++
>   4 files changed, 58 insertions(+), 95 deletions(-)
>
Russell King (Oracle) Jan. 17, 2021, 10:09 a.m. UTC | #2
On Sun, Jan 17, 2021 at 12:57:55PM +0800, Kefeng Wang wrote:
> Correct Russell's mail address (from linux@armlinux.org.uk to
> rmk+kernel@armlinux.org.uk, should update the MAINTAINERS)

No. MAINTAINERS is correct.

> On 2021/1/15 13:46, Kefeng Wang wrote:
> > Use the same implementation of initrd reserve to avoid duplication.
> > 
> > v3:
> > - split into four patches, suggested-by Palmer Dabbelt
> > v2:
> > - fix build error found by kernel test robot
> > 
> > Kefeng Wang (4):
> >    initrd: Add the preprocessor guard in initrd.h
> >    initramfs: Provide a common initrd reserve function
> >    ARM: Covert to reserve_initrd_mem()
> >    riscv: Covert to reserve_initrd_mem()
> > 
> >   arch/arm/mm/init.c     | 43 +--------------------------------
> >   arch/riscv/mm/init.c   | 54 +-----------------------------------------
> >   include/linux/initrd.h | 11 +++++++++
> >   init/initramfs.c       | 45 +++++++++++++++++++++++++++++++++++
> >   4 files changed, 58 insertions(+), 95 deletions(-)
> > 
>
Russell King (Oracle) Jan. 18, 2021, 9:17 a.m. UTC | #3
On Mon, Jan 18, 2021 at 09:01:40AM +0800, Kefeng Wang wrote:
> 
> On 2021/1/17 18:09, Russell King - ARM Linux admin wrote:
> > On Sun, Jan 17, 2021 at 12:57:55PM +0800, Kefeng Wang wrote:
> > > Correct Russell's mail address (from linux@armlinux.org.uk to
> > > rmk+kernel@armlinux.org.uk, should update the MAINTAINERS)
> > No. MAINTAINERS is correct.
> 
> I got following message,  so I check mail of your recent patches, and send a
> new one.
> 
> Please ignore it, there may be some other problems.
> 
> "*Delivery has failed to these recipients or groups:*
> 
> linux@armlinux.org.uk <mailto:linux@armlinux.org.uk>
> A communication failure occurred during the delivery of this message. Please
> to resend the message later. If the problem continues, contact your
> helpdesk."

That is a most unhelpful bounce message - I suppose it's designed for
non-technical people to ensure that the problem can't be resolved.

From what I can see from my end, every attempt involving your email
address last week (wangkefeng.wang@huawei.com) has been successful, so
I suspect the problem is not at my end.

In any case, all @armlinux.org.uk addresses hit the same server, so
if there's a "communication failure" for the domain, it would affect
all local-parts equally.
Palmer Dabbelt Jan. 22, 2021, 3:54 a.m. UTC | #4
On Thu, 14 Jan 2021 21:46:02 PST (-0800), wangkefeng.wang@huawei.com wrote:
> Use the same implementation of initrd reserve to avoid duplication.
>
> v3:
> - split into four patches, suggested-by Palmer Dabbelt
> v2:
> - fix build error found by kernel test robot
>
> Kefeng Wang (4):
>   initrd: Add the preprocessor guard in initrd.h
>   initramfs: Provide a common initrd reserve function
>   ARM: Covert to reserve_initrd_mem()
>   riscv: Covert to reserve_initrd_mem()
>
>  arch/arm/mm/init.c     | 43 +--------------------------------
>  arch/riscv/mm/init.c   | 54 +-----------------------------------------
>  include/linux/initrd.h | 11 +++++++++
>  init/initramfs.c       | 45 +++++++++++++++++++++++++++++++++++
>  4 files changed, 58 insertions(+), 95 deletions(-)

Thanks. I have a shared tag with the first two on top of 5.11-rc2 (the start of
my for-next), which I just merged into the riscv/for-next.

git://git.kernel.org/pub/scm/linux/kernel/git/palmer/linux.git -b shared-lib-reserve_initrd_mem

I'm happy to take the ARM patch if that's easier on your end, but for now I'm
dropping it.
Kefeng Wang Jan. 22, 2021, 7:29 a.m. UTC | #5
On 2021/1/18 17:17, Russell King - ARM Linux admin wrote:
> On Mon, Jan 18, 2021 at 09:01:40AM +0800, Kefeng Wang wrote:
>> On 2021/1/17 18:09, Russell King - ARM Linux admin wrote:
>>> On Sun, Jan 17, 2021 at 12:57:55PM +0800, Kefeng Wang wrote:
>>>> Correct Russell's mail address (from linux@armlinux.org.uk to
>>>> rmk+kernel@armlinux.org.uk, should update the MAINTAINERS)
>>> No. MAINTAINERS is correct.
>> I got following message,  so I check mail of your recent patches, and send a
>> new one.
>>
>> Please ignore it, there may be some other problems.
>>
>> "*Delivery has failed to these recipients or groups:*
>>
>> linux@armlinux.org.uk <mailto:linux@armlinux.org.uk>
>> A communication failure occurred during the delivery of this message. Please
>> to resend the message later. If the problem continues, contact your
>> helpdesk."
> That is a most unhelpful bounce message - I suppose it's designed for
> non-technical people to ensure that the problem can't be resolved.
>
> >From what I can see from my end, every attempt involving your email
> address last week (wangkefeng.wang@huawei.com) has been successful, so
> I suspect the problem is not at my end.

ok,thank you for letting me know that the email has been received,

any comment about the ARM part in the patchset  ;)

>
> In any case, all @armlinux.org.uk addresses hit the same server, so
> if there's a "communication failure" for the domain, it would affect
> all local-parts equally.
>