From: Michael Ellerman <mpe@ellerman•id.au>
To: Chris Packham <Chris.Packham@alliedtelesis•co.nz>,
"christophe.leroy\@c-s.fr" <christophe.leroy@c-s•fr>,
"paulus\@samba.org" <paulus@samba•org>,
"benh\@kernel.crashing.org" <benh@kernel•crashing.org>,
"malat\@debian.org" <malat@debian•org>
Cc: "linuxppc-dev@lists•ozlabs.org" <linuxppc-dev@lists•ozlabs.org>,
"linux-kernel@vger•kernel.org" <linux-kernel@vger•kernel.org>
Subject: Re: [PATCH v3] powerpc: Support CMDLINE_EXTEND
Date: Thu, 07 Nov 2019 22:21:47 +1100 [thread overview]
Message-ID: <87eeyk53uc.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <46da00814535270a2b525de1f75afc79f3abbf5c.camel@alliedtelesis.co.nz>
Chris Packham <Chris.Packham@alliedtelesis•co.nz> writes:
> Hi All,
>
> On Fri, 2019-08-02 at 06:40 +0200, Christophe Leroy wrote:
>>
>> Le 02/08/2019 à 00:50, Chris Packham a écrit :
>> > Bring powerpc in line with other architectures that support extending or
>> > overriding the bootloader provided command line.
>> >
>> > The current behaviour is most like CMDLINE_FROM_BOOTLOADER where the
>> > bootloader command line is preferred but the kernel config can provide a
>> > fallback so CMDLINE_FROM_BOOTLOADER is the default. CMDLINE_EXTEND can
>> > be used to append the CMDLINE from the kernel config to the one provided
>> > by the bootloader.
>> >
>> > Signed-off-by: Chris Packham <chris.packham@alliedtelesis•co.nz>
>>
>> Reviewed-by: Christophe Leroy <christophe.leroy@c-s•fr>
>
> Just going over some old patches this doesn't appear to be in next. Is
> there anything stopping it from being accepted?
Just me not being overloaded :/, sorry.
Have put it in my next-test branch, which means it should appear in next
in the next few days.
cheers
next prev parent reply other threads:[~2019-11-07 11:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-01 22:50 [PATCH v3] powerpc: Support CMDLINE_EXTEND Chris Packham
2019-08-02 4:40 ` Christophe Leroy
2019-09-26 23:54 ` Chris Packham
2019-11-07 3:18 ` Chris Packham
2019-11-07 11:21 ` Michael Ellerman [this message]
2019-11-14 9:07 ` Michael Ellerman
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=87eeyk53uc.fsf@mpe.ellerman.id.au \
--to=mpe@ellerman$(echo .)id.au \
--cc=Chris.Packham@alliedtelesis$(echo .)co.nz \
--cc=benh@kernel$(echo .)crashing.org \
--cc=christophe.leroy@c-s$(echo .)fr \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=malat@debian$(echo .)org \
--cc=paulus@samba$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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