public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Dmitry Rokosov <ddrokosov@sberdevices.ru>
Cc: linux-serial@vger.kernel.org, xianwei.zhao@amlogic.com,
	devicetree@vger.kernel.org, khilman@baylibre.com,
	kelvin.zhang@amlogic.com, linux-kernel@vger.kernel.org,
	conor+dt@kernel.org, jbrunet@baylibre.com,
	gregkh@linuxfoundation.org, robh+dt@kernel.org,
	jirislaby@kernel.org, rockosov@gmail.com,
	krzysztof.kozlowski+dt@linaro.org,
	martin.blumenstingl@googlemail.com, neil.armstrong@linaro.org,
	linux-arm-kernel@lists.infradead.org, kernel@sberdevices.ru,
	linux-amlogic@lists.infradead.org
Subject: Re: [PATCH v1 4/5] dt-bindings: serial: amlogic,meson-uart: support Amlogic A1
Date: Wed, 5 Jul 2023 13:00:01 -0600	[thread overview]
Message-ID: <168858360022.1592604.9922710628917242811.robh@kernel.org> (raw)
In-Reply-To: <20230704135936.14697-5-ddrokosov@sberdevices.ru>


On Tue, 04 Jul 2023 16:59:35 +0300, Dmitry Rokosov wrote:
> Introduce meson uart serial bindings for A1 SoC family.
> 
> Signed-off-by: Dmitry Rokosov <ddrokosov@sberdevices.ru>
> ---
>  .../devicetree/bindings/serial/amlogic,meson-uart.yaml          | 2 ++
>  1 file changed, 2 insertions(+)
> 

Acked-by: Rob Herring <robh@kernel.org>


  reply	other threads:[~2023-07-05 19:00 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-04 13:59 [PATCH v1 0/5] tty: serial: meson: support ttyS devname Dmitry Rokosov
2023-07-04 13:59 ` [PATCH v1 1/5] tty: serial: meson: use dev_err_probe Dmitry Rokosov
2023-07-04 13:59 ` [PATCH v1 2/5] tty: serial: meson: redesign the module to platform_driver Dmitry Rokosov
2023-07-04 14:46   ` neil.armstrong
2023-07-04 15:19     ` Dmitry Rokosov
2023-07-04 17:06       ` Dmitry Rokosov
2023-07-04 13:59 ` [PATCH v1 3/5] tty: serial: meson: apply ttyS devname instead of ttyAML for new SoCs Dmitry Rokosov
2023-07-04 14:42   ` neil.armstrong
2023-07-04 14:59     ` Dmitry Rokosov
2023-07-04 15:29       ` neil.armstrong
2023-07-04 16:00         ` Dmitry Rokosov
2023-07-04 16:57   ` Conor Dooley
2023-07-04 17:13     ` Dmitry Rokosov
2023-07-04 19:14       ` Conor Dooley
2023-07-04 13:59 ` [PATCH v1 4/5] dt-bindings: serial: amlogic,meson-uart: support Amlogic A1 Dmitry Rokosov
2023-07-05 19:00   ` Rob Herring [this message]
2023-07-04 13:59 ` [PATCH v1 5/5] arm64: dts: meson: a1: change uart compatible string Dmitry Rokosov
2023-07-04 17:02   ` Conor Dooley
2023-07-04 17:08     ` Dmitry Rokosov
2023-07-04 17:10       ` Conor Dooley
2023-07-04 17:19         ` Dmitry Rokosov
2023-07-05  9:46           ` Dmitry Rokosov

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=168858360022.1592604.9922710628917242811.robh@kernel.org \
    --to=robh@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=ddrokosov@sberdevices.ru \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jbrunet@baylibre.com \
    --cc=jirislaby@kernel.org \
    --cc=kelvin.zhang@amlogic.com \
    --cc=kernel@sberdevices.ru \
    --cc=khilman@baylibre.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=martin.blumenstingl@googlemail.com \
    --cc=neil.armstrong@linaro.org \
    --cc=robh+dt@kernel.org \
    --cc=rockosov@gmail.com \
    --cc=xianwei.zhao@amlogic.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