public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pratyush Brahma <quic_pbrahma@quicinc.com>
To: "Daniel Walker (danielwa)" <danielwa@cisco.com>
Cc: "akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	"christophe.leroy@c-s.fr" <christophe.leroy@c-s.fr>,
	"dwalker@fifo99.com" <dwalker@fifo99.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
	"maksym.kokhan@globallogic.com" <maksym.kokhan@globallogic.com>,
	"mpe@ellerman.id.au" <mpe@ellerman.id.au>,
	"robh+dt@kernel.org" <robh+dt@kernel.org>,
	"tomas.mudrunka@gmail.com" <tomas.mudrunka@gmail.com>,
	"xe-linux-external(mailer list)" <xe-linux-external@cisco.com>,
	Pavan Kondeti <quic_pkondeti@quicinc.com>,
	<quic_guptap@quicinc.com>, <quic_ylal@quicinc.com>,
	<quic_vjitta@quicinc.com>
Subject: Re: [PATCH 1/4] add generic builtin command line
Date: Thu, 19 Oct 2023 12:13:57 +0530	[thread overview]
Message-ID: <d752e44a-d420-3bb4-e8fc-c8eee7304675@quicinc.com> (raw)
In-Reply-To: <ZS6YIjZznHMojNLO@goliath>


On 17-10-2023 19:51, Daniel Walker (danielwa) wrote:
> On Tue, Oct 17, 2023 at 04:10:42PM +0530, Pratyush Brahma wrote:
>> For such a usecase, the CONFIG_CMDLINE_PREPEND seems to be quite useful as
>> it would help to stitch bootloader
>> and the desired build variant's configs together. Can you please help to
>> merge this patch?
> Yes, your at least the second person that's asked for it, and it's been on my
> list for some time to release again. I'll try to release it as soon as possible.
>
> Daniel

Thanks Daniel.

Please have this config support for arm64 as well. Previously arm64 used 
to support CONFIG_CMDLINE_EXTEND
which was useful for our usecase. However it was dropped from commit 
cae118b6acc309539b33339e846cbb19187c164c
referring to your patch series as an alternative. Hence the need.

Pratyush

  reply	other threads:[~2023-10-19  6:44 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-19 23:24 [PATCH 1/4] add generic builtin command line Daniel Walker
2019-03-20 22:53 ` Andrew Morton
2019-03-20 23:23   ` Daniel Walker
2019-03-21  3:14     ` Andrew Morton
2019-03-21 15:13       ` Daniel Walker
2019-03-21 22:15         ` Andrew Morton
2021-02-15 19:32           ` Daniel Gimpelevich
2021-02-16 17:42             ` Christophe Leroy
2021-02-16 21:20               ` Daniel Gimpelevich
2021-02-16 19:02             ` Daniel Walker
2021-02-17 21:16             ` Andrew Morton
2023-04-17 16:18 ` Tomas Mudrunka
2023-04-17 16:24   ` Daniel Walker (danielwa)
2023-10-17 10:40     ` Pratyush Brahma
2023-10-17 14:21       ` Daniel Walker (danielwa)
2023-10-19  6:43         ` Pratyush Brahma [this message]
2023-11-08 11:33       ` Christophe Leroy
2023-11-08 16:23         ` Daniel Walker (danielwa)

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=d752e44a-d420-3bb4-e8fc-c8eee7304675@quicinc.com \
    --to=quic_pbrahma@quicinc.com \
    --cc=akpm@linux-foundation.org \
    --cc=christophe.leroy@c-s.fr \
    --cc=danielwa@cisco.com \
    --cc=dwalker@fifo99.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=maksym.kokhan@globallogic.com \
    --cc=mpe@ellerman.id.au \
    --cc=quic_guptap@quicinc.com \
    --cc=quic_pkondeti@quicinc.com \
    --cc=quic_vjitta@quicinc.com \
    --cc=quic_ylal@quicinc.com \
    --cc=robh+dt@kernel.org \
    --cc=tomas.mudrunka@gmail.com \
    --cc=xe-linux-external@cisco.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