linux-kernel - Re: [PATCH v2] w1: ds2408: reset on output

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20190403103352.4f36cfee5e577ef017607527@skyboo.net>
Date:   Wed, 3 Apr 2019 10:33:52 +0200
From:   Mariusz Bialonczyk <manio@...boo.net>
To:     Greg Kroah-Hartman <greg@...ah.com>
Cc:     open list <linux-kernel@...r.kernel.org>,
        Jean-Francois Dagenais <jeff.dagenais@...il.com>
Subject: Re: [PATCH v2] w1: ds2408: reset on output_write retry with
 readback

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@...boo.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@...il.com>

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