All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@kernel.org>
To: Conor Dooley <conor+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Michael Turquette <mturquette@baylibre.com>,
	Rob Herring (Arm) <robh@kernel.org>,
	Taichi Sugaya <sugaya.taichi@socionext.com>,
	Takao Orito <orito.takao@socionext.com>
Cc: linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: clock: milbeaut: Drop providers and consumers from example
Date: Mon, 03 Jun 2024 16:32:07 -0700	[thread overview]
Message-ID: <2f9c1628cb01727e2df49287c445190d.sboyd@kernel.org> (raw)
In-Reply-To: <20240520222646.1741958-1-robh@kernel.org>

Quoting Rob Herring (Arm) (2024-05-20 15:26:45)
> Convention for examples is to only show what's covered by the binding,
> so drop the consumer "socionext,milbeaut-usio-uart" and input clock
> provider "fixed-clock" from the example. "socionext,milbeaut-usio-uart"
> is also not documented by a schema which caused a warning.
> 
> Signed-off-by: Rob Herring (Arm) <robh@kernel.org>
> ---

Applied to clk-next

WARNING: multiple messages have this Message-ID (diff)
From: Stephen Boyd <sboyd@kernel.org>
To: Conor Dooley <conor+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Michael Turquette <mturquette@baylibre.com>,
	Rob Herring (Arm) <robh@kernel.org>,
	Taichi Sugaya <sugaya.taichi@socionext.com>,
	Takao Orito <orito.takao@socionext.com>
Cc: linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: clock: milbeaut: Drop providers and consumers from example
Date: Mon, 03 Jun 2024 16:32:07 -0700	[thread overview]
Message-ID: <2f9c1628cb01727e2df49287c445190d.sboyd@kernel.org> (raw)
In-Reply-To: <20240520222646.1741958-1-robh@kernel.org>

Quoting Rob Herring (Arm) (2024-05-20 15:26:45)
> Convention for examples is to only show what's covered by the binding,
> so drop the consumer "socionext,milbeaut-usio-uart" and input clock
> provider "fixed-clock" from the example. "socionext,milbeaut-usio-uart"
> is also not documented by a schema which caused a warning.
> 
> Signed-off-by: Rob Herring (Arm) <robh@kernel.org>
> ---

Applied to clk-next

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2024-06-03 23:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-20 22:26 [PATCH] dt-bindings: clock: milbeaut: Drop providers and consumers from example Rob Herring (Arm)
2024-05-20 22:26 ` Rob Herring (Arm)
2024-05-21 10:18 ` Krzysztof Kozlowski
2024-05-21 10:18   ` Krzysztof Kozlowski
2024-06-03 23:32 ` Stephen Boyd [this message]
2024-06-03 23:32   ` Stephen Boyd

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=2f9c1628cb01727e2df49287c445190d.sboyd@kernel.org \
    --to=sboyd@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=orito.takao@socionext.com \
    --cc=robh@kernel.org \
    --cc=sugaya.taichi@socionext.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 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.