Reword the subsystem bindings section to make sense, from a grammatical
point of view.
Signed-off-by: Geert Uytterhoeven <[email protected]>
---
Documentation/devicetree/bindings/submitting-patches.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/devicetree/bindings/submitting-patches.rst b/Documentation/devicetree/bindings/submitting-patches.rst
index 68129ff09967d5d7..1d11c25249ff5465 100644
--- a/Documentation/devicetree/bindings/submitting-patches.rst
+++ b/Documentation/devicetree/bindings/submitting-patches.rst
@@ -75,8 +75,8 @@ II. For kernel maintainers
binding, and it hasn't received an Acked-by from the devicetree
maintainers after a few weeks, go ahead and take it.
- Subsystem bindings (anything affecting more than a single device)
- then getting a devicetree maintainer to review it is required.
+ For subsystem bindings (anything affecting more than a single device),
+ getting a devicetree maintainer to review it is required.
3) For a series going though multiple trees, the binding patch should be
kept with the driver using the binding.
--
2.25.1
On 3/9/21 5:06 AM, Geert Uytterhoeven wrote:
> Reword the subsystem bindings section to make sense, from a grammatical
> point of view.
>
> Signed-off-by: Geert Uytterhoeven <[email protected]>
Acked-by: Randy Dunlap <[email protected]>
Thanks.
> ---
> Documentation/devicetree/bindings/submitting-patches.rst | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/submitting-patches.rst b/Documentation/devicetree/bindings/submitting-patches.rst
> index 68129ff09967d5d7..1d11c25249ff5465 100644
> --- a/Documentation/devicetree/bindings/submitting-patches.rst
> +++ b/Documentation/devicetree/bindings/submitting-patches.rst
> @@ -75,8 +75,8 @@ II. For kernel maintainers
> binding, and it hasn't received an Acked-by from the devicetree
> maintainers after a few weeks, go ahead and take it.
>
> - Subsystem bindings (anything affecting more than a single device)
> - then getting a devicetree maintainer to review it is required.
> + For subsystem bindings (anything affecting more than a single device),
> + getting a devicetree maintainer to review it is required.
>
> 3) For a series going though multiple trees, the binding patch should be
> kept with the driver using the binding.
>
--
~Randy
Geert Uytterhoeven <[email protected]> writes:
> Reword the subsystem bindings section to make sense, from a grammatical
> point of view.
>
> Signed-off-by: Geert Uytterhoeven <[email protected]>
> ---
> Documentation/devicetree/bindings/submitting-patches.rst | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/submitting-patches.rst b/Documentation/devicetree/bindings/submitting-patches.rst
> index 68129ff09967d5d7..1d11c25249ff5465 100644
> --- a/Documentation/devicetree/bindings/submitting-patches.rst
> +++ b/Documentation/devicetree/bindings/submitting-patches.rst
> @@ -75,8 +75,8 @@ II. For kernel maintainers
> binding, and it hasn't received an Acked-by from the devicetree
> maintainers after a few weeks, go ahead and take it.
>
> - Subsystem bindings (anything affecting more than a single device)
> - then getting a devicetree maintainer to review it is required.
> + For subsystem bindings (anything affecting more than a single device),
> + getting a devicetree maintainer to review it is required.
Applied, thanks.
jon