From: Jae Hyun Yoo <quic_jaehyoo@quicinc.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Rob Herring <robh+dt@kernel.org>, Joel Stanley <joel@jms.id.au>,
Andrew Jeffery <andrew@aj.id.au>, Andrew Lunn <andrew@lunn.ch>
Cc: Jamie Iles <quic_jiles@quicinc.com>,
Graeme Gregory <quic_ggregory@quicinc.com>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-aspeed@lists.ozlabs.org>
Subject: Re: [PATCH v3] ARM: dts: aspeed: add Nuvia DC-SCM BMC
Date: Sun, 27 Mar 2022 13:24:14 -0700 [thread overview]
Message-ID: <92b381f7-6a4b-1db1-ea00-7bbc8c4b0f84@quicinc.com> (raw)
In-Reply-To: <d0044322-72d8-1348-9898-dc91e3192e94@kernel.org>
[...]
>> + chosen {
>> + stdout-path = &uart5;
>> + bootargs = "console=ttyS4,115200n8";
>
> After adding stdout-path, please remove bootargs.
Can I keep the default bootargs for a case if CONFIG_CMDLINE_FORCE
is enabled?
Best Regards,
Jae
>
> Best regards,
> Krzysztof
WARNING: multiple messages have this Message-ID (diff)
From: Jae Hyun Yoo <quic_jaehyoo@quicinc.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Rob Herring <robh+dt@kernel.org>, Joel Stanley <joel@jms.id.au>,
Andrew Jeffery <andrew@aj.id.au>, Andrew Lunn <andrew@lunn.ch>
Cc: Jamie Iles <quic_jiles@quicinc.com>,
Graeme Gregory <quic_ggregory@quicinc.com>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-aspeed@lists.ozlabs.org>
Subject: Re: [PATCH v3] ARM: dts: aspeed: add Nuvia DC-SCM BMC
Date: Sun, 27 Mar 2022 13:24:14 -0700 [thread overview]
Message-ID: <92b381f7-6a4b-1db1-ea00-7bbc8c4b0f84@quicinc.com> (raw)
In-Reply-To: <d0044322-72d8-1348-9898-dc91e3192e94@kernel.org>
[...]
>> + chosen {
>> + stdout-path = &uart5;
>> + bootargs = "console=ttyS4,115200n8";
>
> After adding stdout-path, please remove bootargs.
Can I keep the default bootargs for a case if CONFIG_CMDLINE_FORCE
is enabled?
Best Regards,
Jae
>
> Best regards,
> Krzysztof
_______________________________________________
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:[~2022-03-27 20:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-25 19:02 [PATCH v3] ARM: dts: aspeed: add Nuvia DC-SCM BMC Jae Hyun Yoo
2022-03-25 19:02 ` Jae Hyun Yoo
2022-03-27 18:55 ` Krzysztof Kozlowski
2022-03-27 18:55 ` Krzysztof Kozlowski
2022-03-27 20:24 ` Jae Hyun Yoo [this message]
2022-03-27 20:24 ` Jae Hyun Yoo
2022-03-28 7:13 ` Krzysztof Kozlowski
2022-03-28 7:13 ` Krzysztof Kozlowski
2022-03-28 14:15 ` Jae Hyun Yoo
2022-03-28 14:15 ` Jae Hyun Yoo
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=92b381f7-6a4b-1db1-ea00-7bbc8c4b0f84@quicinc.com \
--to=quic_jaehyoo@quicinc.com \
--cc=andrew@aj.id.au \
--cc=andrew@lunn.ch \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=quic_ggregory@quicinc.com \
--cc=quic_jiles@quicinc.com \
--cc=robh+dt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.