devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: "Andreas Färber" <afaerber@suse.de>
Cc: linux-kernel@vger.kernel.org,
	linux-realtek-soc@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH v4 1/3] dt-bindings: arm: realtek: Convert comments to descriptions
Date: Thu, 9 Jul 2020 17:14:29 -0600	[thread overview]
Message-ID: <20200709231429.GA1075098@bogus> (raw)
In-Reply-To: <20200622125527.24207-2-afaerber@suse.de>

On Mon, 22 Jun 2020 14:55:24 +0200, Andreas Färber wrote:
> Turn the SoC-level comments into description properties.
> 
> Signed-off-by: Andreas Färber <afaerber@suse.de>
> ---
>  v4: New
> 
>  .../devicetree/bindings/arm/realtek.yaml      | 24 +++++++++----------
>  1 file changed, 12 insertions(+), 12 deletions(-)
> 

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

  reply	other threads:[~2020-07-09 23:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-22 12:55 [PATCH v4 0/3] arm64: dts: realtek: Initial RTD1319 and Pym Particles support Andreas Färber
2020-06-22 12:55 ` [PATCH v4 1/3] dt-bindings: arm: realtek: Convert comments to descriptions Andreas Färber
2020-07-09 23:14   ` Rob Herring [this message]
2020-06-22 12:55 ` [PATCH v4 2/3] dt-bindings: arm: realtek: Document RTD1319 and Realtek Pym Particles EVB Andreas Färber
2020-07-09 23:14   ` Rob Herring
2020-06-22 12:55 ` [PATCH v4 3/3] arm64: dts: realtek: Add RTD1319 SoC " Andreas Färber
  -- strict thread matches above, loose matches on Subject: below --
2020-06-20 23:32 [PATCH v4 0/3] arm64: dts: realtek: Initial RTD1319 and Pym Particles support Andreas Färber
2020-06-20 23:32 ` [PATCH v4 1/3] dt-bindings: arm: realtek: Convert comments to descriptions Andreas Färber
2020-06-27  6:42   ` James Tai [戴志峰]

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=20200709231429.GA1075098@bogus \
    --to=robh@kernel.org \
    --cc=afaerber@suse.de \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-realtek-soc@lists.infradead.org \
    --cc=robh+dt@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 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).