linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@kernel.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
	Rob Herring <robh+dt@kernel.org>
Cc: Peter Rosin <peda@axentia.se>, Maxime Ripard <mripard@kernel.org>,
	linux-i2c@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: i2c: i2c-mux: Remove reset-active-low from ssd1307fb examples
Date: Fri, 28 May 2021 16:07:51 +0200	[thread overview]
Message-ID: <YLD5N1OMXFg3yHp9@kunai> (raw)
In-Reply-To: <20210528111049.1804800-1-geert@linux-m68k.org>

[-- Attachment #1: Type: text/plain, Size: 1887 bytes --]

On Fri, May 28, 2021 at 01:10:49PM +0200, Geert Uytterhoeven wrote:
> The "reset-active-low" property was removed from the ssd1307fb bindings
> in commit 519b4dba586198ee ("fbdev: ssd1307fb: Remove reset-active-low
> from the DT binding document") and from the ssd1307fb binding examples
> in commit 7d7e58d30e046d34 ("dt-bindings: display: ssd1307fb: Remove
> reset-active-low from examples").
> 
> Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>

Now we have a conflict with this series from Rob: "[PATCH v2 0/6]
dt-bindings: Convert mux bindings to schema"

My suggestion would be that Rob adds this on top of his series?
Or he provides an immutable branch for me, so I can apply this patch on
top then?

> ---
>  Documentation/devicetree/bindings/i2c/i2c-mux-gpio.txt  | 1 -
>  Documentation/devicetree/bindings/i2c/i2c-mux-gpmux.txt | 1 -
>  2 files changed, 2 deletions(-)
> 
> diff --git a/Documentation/devicetree/bindings/i2c/i2c-mux-gpio.txt b/Documentation/devicetree/bindings/i2c/i2c-mux-gpio.txt
> index 21da3ecbb3700c06..1bf267302251bb63 100644
> --- a/Documentation/devicetree/bindings/i2c/i2c-mux-gpio.txt
> +++ b/Documentation/devicetree/bindings/i2c/i2c-mux-gpio.txt
> @@ -62,7 +62,6 @@ Example:
>  				reg = <0x3c>;
>  				pwms = <&pwm 4 3000>;
>  				reset-gpios = <&gpio2 7 1>;
> -				reset-active-low;
>  			};
>  		};
>  
> diff --git a/Documentation/devicetree/bindings/i2c/i2c-mux-gpmux.txt b/Documentation/devicetree/bindings/i2c/i2c-mux-gpmux.txt
> index 8b444b94e92fde83..51356fdf2becc3f6 100644
> --- a/Documentation/devicetree/bindings/i2c/i2c-mux-gpmux.txt
> +++ b/Documentation/devicetree/bindings/i2c/i2c-mux-gpmux.txt
> @@ -80,7 +80,6 @@ Example:
>  				reg = <0x3c>;
>  				pwms = <&pwm 4 3000>;
>  				reset-gpios = <&gpio2 7 1>;
> -				reset-active-low;
>  			};
>  		};
>  
> -- 
> 2.25.1
> 

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2021-05-28 14:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-28 11:10 [PATCH] dt-bindings: i2c: i2c-mux: Remove reset-active-low from ssd1307fb examples Geert Uytterhoeven
2021-05-28 14:07 ` Wolfram Sang [this message]
2021-05-28 14:25   ` Geert Uytterhoeven
2021-05-28 14:51     ` Wolfram Sang
2021-06-04 20:41 ` Wolfram Sang

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=YLD5N1OMXFg3yHp9@kunai \
    --to=wsa@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=mripard@kernel.org \
    --cc=peda@axentia.se \
    --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).