From: Jean-Francois Dagenais <jeff.dagenais@gmail.com>
To: open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] w1: ds2408: reset on output_write retry with readback
Date: Thu, 28 Mar 2019 08:17:49 -0400 [thread overview]
Message-ID: <49DF2FF4-FB5E-4FB8-94E3-BE14E5C2DEAF@gmail.com> (raw)
In-Reply-To: <20190327165317.GA3137@kroah.com>
** resending to list only because of bounce **
Hi Greg,
> On Mar 27, 2019, at 12:53, Greg Kroah-Hartman <greg@kroah.com> wrote:
>
> On Thu, Mar 21, 2019 at 11:18:27AM -0400, Jean-Francois Dagenais wrote:
>> Originally
>> Reported-by: Mariusz Bialonczyk <manio@skyboo.net>
>
> That needs to go down in the signed-off-by area.
Noted.
>
> Also, please resend this series in a way that I can apply it. You
> didn't say what the order was for the v2 patches.
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.
Cheers!
next prev parent reply other threads:[~2019-03-28 12:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-18 9:27 [PATCH 0/2] w1: DS2408 fixes Mariusz Bialonczyk
2019-03-18 9:27 ` [PATCH 1/2] w1: ds2408: add a missing reset when retrying in output_write() Mariusz Bialonczyk
2019-03-19 14:21 ` Jean-Francois Dagenais
2019-03-19 14:25 ` Jean-Francois Dagenais
2019-03-21 10:55 ` Mariusz Bialonczyk
2019-03-21 15:18 ` [PATCH v2] w1: ds2408: reset on output_write retry with readback Jean-Francois Dagenais
2019-03-27 16:53 ` Greg Kroah-Hartman
2019-03-28 12:17 ` Jean-Francois Dagenais [this message]
2019-04-03 8:33 ` Mariusz Bialonczyk
2019-03-18 9:27 ` [PATCH 2/2] w1: fix the resume command API Mariusz Bialonczyk
2019-03-19 13:21 ` Jean-Francois Dagenais
2019-03-19 14:21 ` Evgeniy Polyakov
2019-03-21 10:11 ` Mariusz Bialonczyk
2019-03-21 10:52 ` [PATCH v2] " Mariusz Bialonczyk
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=49DF2FF4-FB5E-4FB8-94E3-BE14E5C2DEAF@gmail.com \
--to=jeff.dagenais@gmail.com \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®