All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zev Weiss <zev@bewilderbeest.net>
To: Wolfram Sang <wsa@kernel.org>, Peter Rosin <peda@axentia.se>,
	linux-i2c@vger.kernel.org, Guenter Roeck <linux@roeck-us.net>,
	Rob Herring <robh+dt@kernel.org>,
	openbmc@lists.ozlabs.org, linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH v2 0/2] ic2: mux: pca9541: add delayed-release support
Date: Mon, 21 Mar 2022 15:32:43 -0700	[thread overview]
Message-ID: <Yjj9C5PgBfgmXyp7@hatter.bewilderbeest.net> (raw)
In-Reply-To: <YjRmUokDFPezGI5B@shikoro>

On Fri, Mar 18, 2022 at 04:00:34AM PDT, Wolfram Sang wrote:
>
>Can someone give me a summary What is the status of this series?
>

I had been hoping Peter might offer any further thoughts on my last 
email regarding the feasibility/proper approach for implementing some 
sort of automated avoidance of the problem scenario he pointed out -- or 
alternately, if we think a written warning in the bindings is 
sufficient, I can send a v3 with that incorporated.


Thanks,
Zev


      reply	other threads:[~2022-03-21 22:52 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-01  0:18 [PATCH v2 0/2] ic2: mux: pca9541: add delayed-release support Zev Weiss
2022-02-01  0:18 ` Zev Weiss
2022-02-01  0:18 ` [PATCH v2 1/2] i2c: " Zev Weiss
2022-02-01  0:18   ` Zev Weiss
2022-02-01  0:18 ` [PATCH v2 2/2] dt-bindings: i2c: add nxp,pca9541 release-delay-us property Zev Weiss
2022-02-01  0:18   ` [PATCH v2 2/2] dt-bindings: i2c: add nxp, pca9541 " Zev Weiss
2022-02-09 21:47   ` [PATCH v2 2/2] dt-bindings: i2c: add nxp,pca9541 " Rob Herring
2022-02-09 21:47     ` Rob Herring
2022-02-28  8:43 ` [PATCH v2 0/2] ic2: mux: pca9541: add delayed-release support Zev Weiss
2022-02-28  8:43   ` Zev Weiss
2022-02-28 13:57   ` Guenter Roeck
2022-02-28 13:57     ` Guenter Roeck
2022-02-28 17:11     ` Zev Weiss
2022-02-28 17:11       ` Zev Weiss
2022-02-28 17:19       ` Wolfram Sang
2022-02-28 17:19         ` Wolfram Sang
2022-02-28 18:10       ` Guenter Roeck
2022-02-28 18:10         ` Guenter Roeck
2022-02-28 21:54 ` Peter Rosin
2022-02-28 21:54   ` Peter Rosin
2022-02-28 22:38   ` Zev Weiss
2022-02-28 22:38     ` Zev Weiss
2022-03-02 14:43     ` Peter Rosin
2022-03-02 14:43       ` Peter Rosin
2022-03-03  0:43       ` Zev Weiss
2022-03-03  0:43         ` Zev Weiss
2022-03-18 11:00         ` Wolfram Sang
2022-03-18 11:00           ` Wolfram Sang
2022-03-21 22:32           ` Zev Weiss [this message]

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=Yjj9C5PgBfgmXyp7@hatter.bewilderbeest.net \
    --to=zev@bewilderbeest.net \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=openbmc@lists.ozlabs.org \
    --cc=peda@axentia.se \
    --cc=robh+dt@kernel.org \
    --cc=wsa@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 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.