[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <DM6PR04MB6059A17BAFA1B0AE939FFBF98D660@DM6PR04MB6059.namprd04.prod.outlook.com>
Date: Wed, 13 Feb 2019 11:24:09 +0000
From: Anup Patel <Anup.Patel@....com>
To: Mike Rapoport <rppt@...ux.ibm.com>
CC: Palmer Dabbelt <palmer@...ive.com>,
Albert Ou <aou@...s.berkeley.edu>,
Atish Patra <Atish.Patra@....com>,
Paul Walmsley <paul.walmsley@...ive.com>,
Christoph Hellwig <hch@...radead.org>,
"linux-riscv@...ts.infradead.org" <linux-riscv@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH v5 1/6] RISC-V: Move free_initrd_mem() to kernel/setup.c
> -----Original Message-----
> From: Mike Rapoport [mailto:rppt@...ux.ibm.com]
> Sent: Wednesday, February 13, 2019 3:30 PM
> To: Anup Patel <Anup.Patel@....com>
> Cc: Palmer Dabbelt <palmer@...ive.com>; Albert Ou
> <aou@...s.berkeley.edu>; Atish Patra <Atish.Patra@....com>; Paul
> Walmsley <paul.walmsley@...ive.com>; Christoph Hellwig
> <hch@...radead.org>; linux-riscv@...ts.infradead.org; linux-
> kernel@...r.kernel.org
> Subject: Re: [PATCH v5 1/6] RISC-V: Move free_initrd_mem() to
> kernel/setup.c
>
> On Wed, Feb 13, 2019 at 08:07:17AM +0000, Anup Patel wrote:
> > We move free_initrd_mem() to kernel/setup.c so that all initrd related
> > functions are in one place.
>
> A few patches after you move setup_bootmem() that calls setup_initrd() to
> mm/init.c. I'd say it makes more sense to move setup_intird() to mm/init.c.
Makes sense. I will drop this patch and I will move setup_initrd() to
mm/init.c along with setup_bootmem() because setup_bootmem()
depends on setup_initrd().
Regards,
Anup
Powered by blists - more mailing lists