devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: "Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>
Cc: devicetree@vger.kernel.org, linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH v2 1/2] arm64: dts: renesas: draak: Make HDMI the default video input
Date: Tue, 21 Nov 2023 09:51:31 +0100	[thread overview]
Message-ID: <CAMuHMdX-vZJTj+kC53L31cHqewq1fKhLS-MT--GUurPkLf4GwQ@mail.gmail.com> (raw)
In-Reply-To: <20231022181910.898040-2-niklas.soderlund+renesas@ragnatech.se>

On Sun, Oct 22, 2023 at 8:19 PM Niklas Söderlund
<niklas.soderlund+renesas@ragnatech.se> wrote:
> Most Gen3 R-Car devices have HDMI as the default video input source,
> align Draak with them and make HDMI the default.
>
> Signed-off-by: Niklas Söderlund <niklas.soderlund+renesas@ragnatech.se>
> ---
> * Changes since v1
> - Split moving the incorrect bus properties to separate patch.

Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
i.e. will queue in renesas-devel for v6.8.

Gr{oetje,eeting}s,

                        Geert

-- 
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

  reply	other threads:[~2023-11-21  8:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-22 18:19 [PATCH v2 0/2] arm64: dts: renesas: draak: Make HDMI default video source Niklas Söderlund
2023-10-22 18:19 ` [PATCH v2 1/2] arm64: dts: renesas: draak: Make HDMI the default video input Niklas Söderlund
2023-11-21  8:51   ` Geert Uytterhoeven [this message]
2023-10-22 18:19 ` [PATCH v2 2/2] arm64: dts: renesas: draak: Move HDMI bus properties to correct node Niklas Söderlund
2023-11-21  8:52   ` Geert Uytterhoeven

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=CAMuHMdX-vZJTj+kC53L31cHqewq1fKhLS-MT--GUurPkLf4GwQ@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=niklas.soderlund+renesas@ragnatech.se \
    /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).