From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Zak Hays <zak.hays@lexmark.com>
Cc: "miquel.raynal@bootlin.com" <miquel.raynal@bootlin.com>,
"rui.zhang@intel.com" <rui.zhang@intel.com>,
"amit.kucheria@verdurent.com" <amit.kucheria@verdurent.com>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/2] thermal: armada: fix register offsets for AXP
Date: Mon, 9 Dec 2019 18:11:24 +0100 [thread overview]
Message-ID: <cee7f713-681d-8b03-08e3-3b10da36d2d5@linaro.org> (raw)
In-Reply-To: <BN8PR10MB337975A77D726FDAFA9F13598C580@BN8PR10MB3379.namprd10.prod.outlook.com>
On 09/12/2019 17:58, Zak Hays wrote:
>> On 09/12/2019 17:31, Zak Hays wrote:
>>> Hi Daniel,
>>>
>>>> Hi Zak,
>>>>
>>>> what patch to pick up? V2 or V2?
>>> I'm not sure I entirely understand your question. There are two patches:
>>>
>>> Zachary Hays thermal: armada: fix register offsets for AXP
>>> Zachary Hays thermal: armada: clear reset in armadaxp_init
>>
>> I'm seeing multiple posting of the V2 and reply to V2 with I guess a
>> changelog added.
>>
>> It is very difficult to deal with patches when it is unclear, duplicate
>> series with different changelog.
>>
>> In the future, post a resend version explaining what was missing, so it
>> is easier to understand what is happening. Or send a V3.
>
> Ah. I understand now. I've been fighting email issues trying to get these patches sent and
> inadvertently sent out multiple versions of the same patches. The most recent patches
> are correct. Sorry for that spam. Shouldn't happen again.
>
> Would you like me to resend as V3 for clarity or would you prefer to continue with the
> V2 patches?
A V3 please, so I can pick them up without ambiguity from patchwork.
Thanks!
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2019-12-09 17:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1575485367-18262-1-git-send-email-zhays@lexmark.com>
2019-12-05 14:19 ` Zak Hays
2019-12-09 15:42 ` Daniel Lezcano
2019-12-09 16:31 ` Zak Hays
2019-12-09 16:39 ` Daniel Lezcano
2019-12-09 16:58 ` Zak Hays
2019-12-09 17:11 ` Daniel Lezcano [this message]
[not found] ` <1575485367-18262-2-git-send-email-zhays@lexmark.com>
2019-12-05 14:19 ` [PATCH v2 2/2] thermal: armada: clear reset in armadaxp_init Zak Hays
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=cee7f713-681d-8b03-08e3-3b10da36d2d5@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=amit.kucheria@verdurent.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=miquel.raynal@bootlin.com \
--cc=rui.zhang@intel.com \
--cc=zak.hays@lexmark.com \
/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®