From: "Rob Herring (Arm)" <robh@kernel.org>
To: Kuan-Wei Chiu <visitorckw@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
sre@kernel.org, conor+dt@kernel.org, eleanor15x@gmail.com,
simona@ffwll.ch, airlied@gmail.com, tzimmermann@suse.de,
krzk+dt@kernel.org, gregkh@linuxfoundation.org,
jserv@ccns.ncku.edu.tw, mripard@kernel.org,
linux-input@vger.kernel.org, dri-devel@lists.freedesktop.org,
broonie@kernel.org, maarten.lankhorst@linux.intel.com,
linux-sound@vger.kernel.org, devicetree@vger.kernel.org,
dmitry.torokhov@gmail.com, jirislaby@kernel.org,
lgirdwood@gmail.com, linux-pm@vger.kernel.org
Subject: Re: [PATCH v4 6/6] dt-bindings: display: google,goldfish-fb: Convert to DT schema
Date: Thu, 15 Jan 2026 11:41:58 -0600 [thread overview]
Message-ID: <176849890696.935461.15138796644724079676.robh@kernel.org> (raw)
In-Reply-To: <20260113092602.3197681-7-visitorckw@gmail.com>
On Tue, 13 Jan 2026 09:26:02 +0000, Kuan-Wei Chiu wrote:
> Convert the Android Goldfish Framebuffer binding to DT schema format.
> Update the example node name to 'display' to comply with generic node
> naming standards.
>
> Signed-off-by: Kuan-Wei Chiu <visitorckw@gmail.com>
> ---
> .../bindings/display/google,goldfish-fb.txt | 17 ---------
> .../bindings/display/google,goldfish-fb.yaml | 38 +++++++++++++++++++
> 2 files changed, 38 insertions(+), 17 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/display/google,goldfish-fb.txt
> create mode 100644 Documentation/devicetree/bindings/display/google,goldfish-fb.yaml
>
Applied, thanks!
next prev parent reply other threads:[~2026-01-15 17:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-13 9:25 [PATCH v4 0/6] dt-bindings: goldfish: " Kuan-Wei Chiu
2026-01-13 9:25 ` [PATCH v4 1/6] dt-bindings: serial: google,goldfish-tty: " Kuan-Wei Chiu
2026-01-13 9:25 ` [PATCH v4 2/6] dt-bindings: misc: google,android-pipe: " Kuan-Wei Chiu
2026-01-14 20:27 ` Rob Herring (Arm)
2026-01-13 9:25 ` [PATCH v4 3/6] dt-bindings: input: google,goldfish-events-keypad: " Kuan-Wei Chiu
2026-01-14 7:31 ` Krzysztof Kozlowski
2026-01-20 19:56 ` Dmitry Torokhov
2026-01-13 9:26 ` [PATCH v4 4/6] dt-bindings: power: supply: google,goldfish-battery: " Kuan-Wei Chiu
2026-01-14 7:31 ` Krzysztof Kozlowski
2026-01-13 9:26 ` [PATCH v4 5/6] dt-bindings: sound: google,goldfish-audio: " Kuan-Wei Chiu
2026-01-14 7:31 ` Krzysztof Kozlowski
2026-01-13 9:26 ` [PATCH v4 6/6] dt-bindings: display: google,goldfish-fb: " Kuan-Wei Chiu
2026-01-15 17:41 ` Rob Herring (Arm) [this message]
2026-01-14 21:36 ` (subset) [PATCH v4 0/6] dt-bindings: goldfish: " Mark Brown
2026-01-30 22:24 ` Sebastian Reichel
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=176849890696.935461.15138796644724079676.robh@kernel.org \
--to=robh@kernel.org \
--cc=airlied@gmail.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=eleanor15x@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=jserv@ccns.ncku.edu.tw \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--cc=sre@kernel.org \
--cc=tzimmermann@suse.de \
--cc=visitorckw@gmail.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
all inboxes | Powered by JetHome®