Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Thu, 28 Mar 2019 17:22:33 +0100
From:   Greg KH <greg@kroah.com>
To:     Jean-Francois Dagenais <jeff.dagenais@gmail.com>
Cc:     linux-kernel@vger.kernel.org, zbr@ioremap.net, manio@skyboo.net
Subject: Re: [PATCH v3] w1: ds2408: reset on output_write retry with readback
Message-ID: <20190328162233.GB2173@kroah.com>
References: <20190328122244.32126-1-jeff.dagenais@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20190328122244.32126-1-jeff.dagenais@gmail.com>
User-Agent: Mutt/1.11.4 (2019-03-13)
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Thu, Mar 28, 2019 at 08:22:44AM -0400, Jean-Francois Dagenais wrote:
> When we have success in 'Channel Access Write' but reading back latch
> states fails, a write is retried without doing a proper slave reset.
> This leads to protocol errors as the slave treats the next 'Channel
> Access Write' as the continuation of previous command.
> 
> This commit is fixing this by making sure if the retry loop re-runs, a
> reset is performed, whatever the failure (CONFIRM_BYTE or the read
> back).
> 
> The loop was quite due for a cleanup and this change mandated it. By
> isolating the CONFIG_W1_SLAVE_DS2408_READBACK case into it's own
> function, we vastly reduce the visual and branching(runtime and
> compile-time) noise.
> 
> Reported-by: Mariusz Bialonczyk <manio@skyboo.net>
> Tested-by: Mariusz Bialonczyk <manio@skyboo.net>
> Signed-off-by: Jean-Francois Dagenais <jeff.dagenais@gmail.com>
> ---
>  drivers/w1/slaves/w1_ds2408.c | 76 ++++++++++++++++++++++---------------------
>  1 file changed, 39 insertions(+), 37 deletions(-)

What changed from previous versions?  That information always goes below
the --- line.

v4 please.

thanks,

greg k-h