From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-renesas-soc@vger.kernel.org,
Marek Vasut <marek.vasut@mailbox.org>,
Magnus Damm <magnus.damm@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: renesas: sparrow-hawk: don't reserve SWDT
Date: Mon, 20 Oct 2025 21:48:39 +0200 [thread overview]
Message-ID: <aPaSF2lokJ748cTx@shikoro> (raw)
In-Reply-To: <CAMuHMdUCSRKAbD=DfJxfFGpfKTRkt=a2BO+HnwTqALBeeECOkA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 352 bytes --]
> Or better: drop all these swdt = reserved commits?
Maybe. Since Marek is maybe interested in fixing FW...
> TBH, I always had my doubts about making them reserved in the upstream
> DTS, and there does not seem to be much gain in doing so...
No strong opinion here. With "reserved" I think I followed your
suggestion but I personally don't mind.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-10-20 19:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-17 11:51 [PATCH] arm64: dts: renesas: sparrow-hawk: don't reserve SWDT Wolfram Sang
2025-10-17 11:54 ` Marek Vasut
2025-10-20 13:07 ` Geert Uytterhoeven
2025-10-20 19:48 ` Wolfram Sang [this message]
2025-10-21 7:09 ` Geert Uytterhoeven
2025-10-21 13:14 ` Marek Vasut
2025-10-21 13:22 ` Geert Uytterhoeven
2025-10-21 16:07 ` Marek Vasut
2025-10-22 7:01 ` Wolfram Sang
2025-10-27 10:09 ` Geert Uytterhoeven
2025-10-27 18:21 ` Marek Vasut
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=aPaSF2lokJ748cTx@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=krzk+dt@kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=marek.vasut@mailbox.org \
--cc=robh@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.