[PATCH] docs: Fix typo in aspeed-lpc.yaml

Suraj Patil posted 1 patch 10 months ago
There is a newer version of this series
Documentation/devicetree/bindings/mfd/aspeed-lpc.yaml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
[PATCH] docs: Fix typo in aspeed-lpc.yaml
Posted by Suraj Patil 10 months ago
Correct 'Tehchnology' to 'Technology' in the copyright line.

Signed-off-by: Suraj Patil <surajpatil522@gmail.com>
---
 Documentation/devicetree/bindings/mfd/aspeed-lpc.yaml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/devicetree/bindings/mfd/aspeed-lpc.yaml b/Documentation/devicetree/bindings/mfd/aspeed-lpc.yaml
index 5dfe77aca167..d88854e60b7f 100644
--- a/Documentation/devicetree/bindings/mfd/aspeed-lpc.yaml
+++ b/Documentation/devicetree/bindings/mfd/aspeed-lpc.yaml
@@ -1,5 +1,5 @@
 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
-# # Copyright (c) 2021 Aspeed Tehchnology Inc.
+# # Copyright (c) 2021 Aspeed Technology Inc.
 %YAML 1.2
 ---
 $id: http://devicetree.org/schemas/mfd/aspeed-lpc.yaml#
-- 
2.43.0
Re: [PATCH] docs: Fix typo in aspeed-lpc.yaml
Posted by Krzysztof Kozlowski 10 months ago
On 16/02/2025 00:19, Suraj Patil wrote:
> Correct 'Tehchnology' to 'Technology' in the copyright line.
> 
> Signed-off-by: Suraj Patil <surajpatil522@gmail.com>

Why are you sending 4 same patches?

<form letter>
Please use scripts/get_maintainers.pl to get a list of necessary people
and lists to CC. It might happen, that command when run on an older
kernel, gives you outdated entries. Therefore please be sure you base
your patches on recent Linux kernel.

Tools like b4 or scripts/get_maintainer.pl provide you proper list of
people, so fix your workflow. Tools might also fail if you work on some
ancient tree (don't, instead use mainline) or work on fork of kernel
(don't, instead use mainline). Just use b4 and everything should be
fine, although remember about `b4 prep --auto-to-cc` if you added new
patches to the patchset.

You missed at least devicetree list (maybe more), so this won't be
tested by automated tooling. Performing review on untested code might be
a waste of time.

Please kindly resend and include all necessary To/Cc entries.
</form letter>


Best regards,
Krzysztof