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:   Wed, 3 Apr 2019 10:33:52 +0200
From:   Mariusz Bialonczyk <manio@skyboo.net>
To:     Greg Kroah-Hartman <greg@kroah.com>
Cc:     open list <linux-kernel@vger.kernel.org>,
        Jean-Francois Dagenais <jeff.dagenais@gmail.com>
Message-Id: <20190403103352.4f36cfee5e577ef017607527@skyboo.net>
In-Reply-To: <49DF2FF4-FB5E-4FB8-94E3-BE14E5C2DEAF@gmail.com>
References: <20190318092737.8170-1-manio@skyboo.net>
        <20190318092737.8170-2-manio@skyboo.net>
        <10244730-36A8-4DAC-95E5-AD7BDEA32F43@gmail.com>
        <20190327165317.GA3137@kroah.com>
        <49DF2FF4-FB5E-4FB8-94E3-BE14E5C2DEAF@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH v2] w1: ds2408: reset on output_write retry with
 readback
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

Hi Greg,

Exactly as Jean-Francois stated:
> Mariusz can chime in but I believe although it was the same exercise
> that led to his discoveries, each patch can stand alone and be applied
> in any order.
> 
> I will send a v3 without a reply-to-id. Mariusz' patch "[PATCH v2] w1:
> fix the resume command API" can be applied as is unless you need it
> changed or resent.

To sum it all - patches order is irrelevant and the patches to merge are:

mine latest one:
Subject: [PATCH v2] w1: fix the resume command API
Date: Thu, 21 Mar 2019 11:52:55 +0100
Message-ID: <20190321105255.19126-1-manio@skyboo.net>

and Jean's latest one:
Subject: [PATCH v4] w1: ds2408: reset on output_write retry with readback
Date:   Thu, 28 Mar 2019 12:41:11 -0400
Message-Id: <20190328164111.24041-1-jeff.dagenais@gmail.com>

regards,
-- 
Mariusz Białończyk | xmpp/e-mail: manio@skyboo.net
http://manio.skyboo.net | https://github.com/manio