From: Catalin Marinas <catalin.marinas@arm.com>
To: ja.kaisrlik@gmail.com
Cc: will@kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64: update Kconfig to better handle CMDLINE
Date: Sun, 29 Sep 2019 11:16:24 +0100 [thread overview]
Message-ID: <20190929101624.GA94161@MBP.local> (raw)
In-Reply-To: <20190920164249.6935-1-ja.kaisrlik@gmail.com>
On Fri, Sep 20, 2019 at 06:42:49PM +0200, ja.kaisrlik@gmail.com wrote:
> Added a menu to choose how to CMDLINE will be handled. Config strings
> were copied from arm32 port.
This was proposed before but we rejected it. Do you have a good reason,
other than arm32 having it?
https://patchwork.kernel.org/patch/9459341/
--
Catalin
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-09-29 10:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-20 16:42 [PATCH] arm64: update Kconfig to better handle CMDLINE ja.kaisrlik
2019-09-27 13:51 ` Jan Kaisrlik
2019-09-29 10:16 ` Catalin Marinas [this message]
2019-10-01 7:13 ` Jan Kaisrlik
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=20190929101624.GA94161@MBP.local \
--to=catalin.marinas@arm.com \
--cc=ja.kaisrlik@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=will@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).