From: Andreas Schwab <schwab@suse.de>
To: Anup Patel <Anup.Patel@wdc.com>
Cc: Palmer Dabbelt <palmer@sifive.com>,
Albert Ou <aou@eecs.berkeley.edu>,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@infradead.org>,
Atish Patra <Atish.Patra@wdc.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
"linux-riscv\@lists.infradead.org"
<linux-riscv@lists.infradead.org>
Subject: Re: [PATCH v3 6/6] RISC-V: Implement keepinitrd kernel parameter
Date: Tue, 12 Feb 2019 15:07:45 +0100 [thread overview]
Message-ID: <mvmmun1rtfy.fsf@suse.de> (raw)
In-Reply-To: <20190212135942.105008-7-anup.patel@wdc.com> (Anup Patel's message of "Tue, 12 Feb 2019 14:01:19 +0000")
On Feb 12 2019, Anup Patel <Anup.Patel@wdc.com> wrote:
> This patch implements keepinitrd kernel parameter. By default,
> keepinitrd=0 so initrd memory will be freed by default freed but
-freed
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
prev parent reply other threads:[~2019-02-12 14:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-12 14:00 [PATCH v3 0/6] Fixmap support and MM cleanups Anup Patel
2019-02-12 14:00 ` [PATCH v3 1/6] RISC-V: Move free_initrd_mem() to kernel/setup.c Anup Patel
2019-02-12 14:00 ` [PATCH v3 2/6] RISC-V: Setup init_mm before parse_early_param() Anup Patel
2019-02-12 14:00 ` [PATCH v3 3/6] RISC-V: Move setup_bootmem() to mm/init.c Anup Patel
2019-02-12 14:00 ` [PATCH v3 4/6] RISC-V: Move setup_vm() " Anup Patel
2019-02-12 14:00 ` [PATCH v3 5/6] RISC-V: Implement compile-time fixed mappings Anup Patel
2019-02-12 14:01 ` [PATCH v3 6/6] RISC-V: Implement keepinitrd kernel parameter Anup Patel
2019-02-12 14:07 ` Andreas Schwab [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=mvmmun1rtfy.fsf@suse.de \
--to=schwab@suse.de \
--cc=Anup.Patel@wdc.com \
--cc=Atish.Patra@wdc.com \
--cc=aou@eecs.berkeley.edu \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@sifive.com \
--cc=paul.walmsley@sifive.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox