From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Varada Pavani <v.pavani@samsung.com>,
mturquette@baylibre.com, sboyd@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, s.nawrocki@samsung.com,
tomasz.figa@gmail.com
Cc: linux-samsung-soc@vger.kernel.org, alim.akhtar@samsung.com,
aswani.reddy@samsung.com, pankaj.dubey@samsung.com
Subject: Re: [PATCH 1/2] dt-bindings: clock: Fix spelling mistake in 'tesla,fsd-clock.yaml'
Date: Tue, 19 Dec 2023 13:07:06 +0100 [thread overview]
Message-ID: <cb9a6bd4-6c99-4409-9cc7-73b600eb8fce@linaro.org> (raw)
In-Reply-To: <20231219115834.65720-1-v.pavani@samsung.com>
On 19/12/2023 12:58, Varada Pavani wrote:
> Fix typo 'inteernal' to 'internal' in 'Documentation/devicetree/
> bindings/clock/tesla,fsd-clock.yaml'.
>
> Signed-off-by: Varada Pavani <v.pavani@samsung.com>
> ---
> Documentation/devicetree/bindings/clock/tesla,fsd-clock.yaml | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Are there any other typos in that file or in other Samsung clock bindings?
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-12-19 12:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20231219115856epcas5p371abeb4264f60309e597b90954e6d58c@epcas5p3.samsung.com>
2023-12-19 11:58 ` [PATCH 1/2] dt-bindings: clock: Fix spelling mistake in 'tesla,fsd-clock.yaml' Varada Pavani
2023-12-19 11:58 ` [PATCH 2/2] clk: samsung: Fix typo error and extra space Varada Pavani
2023-12-19 12:06 ` Krzysztof Kozlowski
2023-12-26 17:05 ` Varada Pavani
2023-12-27 11:40 ` Krzysztof Kozlowski
2023-12-19 12:07 ` Krzysztof Kozlowski [this message]
2023-12-26 16:57 ` [PATCH 1/2] dt-bindings: clock: Fix spelling mistake in 'tesla,fsd-clock.yaml' Varada Pavani
2023-12-26 18:57 ` Krzysztof Kozlowski
2024-01-23 8:21 ` Krzysztof Kozlowski
2024-01-23 9:54 ` (subset) " Krzysztof Kozlowski
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=cb9a6bd4-6c99-4409-9cc7-73b600eb8fce@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=alim.akhtar@samsung.com \
--cc=aswani.reddy@samsung.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=pankaj.dubey@samsung.com \
--cc=s.nawrocki@samsung.com \
--cc=sboyd@kernel.org \
--cc=tomasz.figa@gmail.com \
--cc=v.pavani@samsung.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