linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: "Koehrer Mathias (ETAS/EES-SL)" <mathias.koehrer@etas.com>
Cc: tyhicks@linux.microsoft.com, "will@kernel.org" <will@kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] arm64: Extend arm64 Kconfig to contain CMDLINE_EXTEND
Date: Thu, 26 Nov 2020 15:11:13 +0000	[thread overview]
Message-ID: <20201126151113.GA6722@gaia> (raw)
In-Reply-To: <1084ae3fcfc40af0dfa5c453513c45744af3184b.camel@etas.com>

On Mon, Nov 02, 2020 at 12:12:19PM +0000, Koehrer Mathias (ETAS/EES-SL) wrote:
> Extend arm64 Kconfig to contain CMDLINE_EXTEND
> 
> The config variable CMDLINE_EXTEND is already available in some
> architectures, however it is missing in arm64.
> This patch adds this config variable for architecture arm64.
> 
> Signed-off-by: Mathias Koehrer <mathias.koehrer@etas.com>

There was at least another patch series proposing CMDLINE_EXTENDED.
Could you please check that to see whether it meets your needs:

https://lore.kernel.org/r/20200921191557.350256-1-tyhicks@linux.microsoft.com/

Tyler's series seems to cover an issue with searching for the "nokaslr"
string in the cmdline arguments when using the extended option.

-- 
Catalin

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      reply	other threads:[~2020-11-26 15:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-02 12:12 [PATCH] arm64: Extend arm64 Kconfig to contain CMDLINE_EXTEND Koehrer Mathias (ETAS/EES-SL)
2020-11-26 15:11 ` Catalin Marinas [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=20201126151113.GA6722@gaia \
    --to=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=mathias.koehrer@etas.com \
    --cc=tyhicks@linux.microsoft.com \
    --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).