From: Ole Orhagen <ole.orhagen@northern.tech>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: linux-arm-kernel@lists.infradead.org, ole@orhagen.no,
kristian.amlie@northern.tech, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Liviu Dudau <liviu.dudau@arm.com>,
Sudeep Holla <sudeep.holla@arm.com>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
Andre Przywara <andre.przywara@arm.com>,
Claudiu Beznea <claudiu.beznea@tuxon.dev>,
Shawn Guo <shawnguo@kernel.org>, Peter Rosin <peda@axentia.se>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] ARM: dts: vexpress: Set stdout-path to serial0 in the chosen node
Date: Tue, 20 Feb 2024 08:30:42 +0100 [thread overview]
Message-ID: <CAD5A3CvRNpAibArAZg11TdfKP62V9Eeb9ccUhiQwWLiGKgk+Sw@mail.gmail.com> (raw)
In-Reply-To: <CACRpkda=b-uZmSfqRLkkC6Lp-JbSoi+YZpwhVn9-RMOPxiXszA@mail.gmail.com>
On Fri, Feb 9, 2024 at 2:02 PM Linus Walleij <linus.walleij@linaro.org> wrote:
>
> On Fri, Feb 9, 2024 at 12:29 PM Ole P. Orhagen
> <ole.orhagen@northern.tech> wrote:
>
> > Specify v2m_serial0 as the device for boot console output through the
> > stdout-path in the chosen node.
> >
> > Signed-off-by: Ole P. Orhagen <ole.orhagen@northern.tech>
>
> It's also the right way to do it.
> Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
>
> Sudeep: are you queueing Vexpress DTS changes or do you want me
> to handle it with other Versatile-ish ARM DTS stuff?
>
> Yours,
> Linus Walleij
Is there anything else I need to do here, or can I consider this a
valid handoff and forget about it?
Yours,
Ole P.
next prev parent reply other threads:[~2024-02-20 7:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-09 11:28 [PATCH 1/1] ARM: dts: vexpress: Set stdout-path to serial0 in the chosen node Ole P. Orhagen
2024-02-09 13:02 ` Linus Walleij
2024-02-20 7:30 ` Ole Orhagen [this message]
2024-02-22 7:04 ` Sudeep Holla
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=CAD5A3CvRNpAibArAZg11TdfKP62V9Eeb9ccUhiQwWLiGKgk+Sw@mail.gmail.com \
--to=ole.orhagen@northern.tech \
--cc=andre.przywara@arm.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kristian.amlie@northern.tech \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liviu.dudau@arm.com \
--cc=lpieralisi@kernel.org \
--cc=ole@orhagen.no \
--cc=peda@axentia.se \
--cc=robh+dt@kernel.org \
--cc=shawnguo@kernel.org \
--cc=sudeep.holla@arm.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;
as well as URLs for NNTP newsgroup(s).