linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zak Hays <zak.hays@lexmark.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
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 16:58:12 +0000	[thread overview]
Message-ID: <BN8PR10MB337975A77D726FDAFA9F13598C580@BN8PR10MB3379.namprd10.prod.outlook.com> (raw)
In-Reply-To: <6c4e79ab-313c-5bb5-1489-329d916bd947@linaro.org>

>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?

>
>> Version 2 of each patch updates the commit message to add a "Signed-off-by"
>> and cleans up the commit message per Miquèl's earlier comments. Otherwise the
>> patches are the same as they were in version 1. The patch below is version 2 of that first patch.
>>
>> Does that answer your question?
>>>
>>> What email is the correct one?
>>>
>>>        Zachary Hays <zhays@lexmark.com>
>>> or
>>>        Zak Hays <zak.hays@lexmark.com>
>>>
>> Both addresses route to the same place but "Zachary Hays <zhays@lexmark.com>" is preferable. Sorry for the confusion.
>>
>>> Also waiting for Miquel to ack the patch.
>>>
>>> Thanks
>>>
>>> -- Daniel
>>>
>>>
>>> On 05/12/2019 15:19, Zak Hays wrote:
>>>> As shown in its device tree, Armada XP has the control1 register at
>>>> 0x184d0, not 0x182d0.
>>>>
>>>> Signed-off-by: Zachary Hays <zhays@lexmark.com>
>>>> ---
>>>> v2: update commit title and add "Signed-off-by"
>>>> ---
>>>>  drivers/thermal/armada_thermal.c | 2 +-
>>>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>>>
>>>> diff --git a/drivers/thermal/armada_thermal.c b/drivers/thermal/armada_thermal.c
>>>> index 709a22f455e9..88363812033c 100644
>>>> --- a/drivers/thermal/armada_thermal.c
>>>> +++ b/drivers/thermal/armada_thermal.c
>>>> @@ -578,7 +578,7 @@ static const struct armada_thermal_data armadaxp_data = {
>>>>         .coef_m = 10000000ULL,
>>>>         .coef_div = 13825,
>>>>         .syscon_status_off = 0xb0,
>>>> -       .syscon_control1_off = 0xd0,
>>>> +       .syscon_control1_off = 0x2d0,
>>>>  };
>>>>
>>>>  static const struct armada_thermal_data armada370_data = {
>>>> --
>>>> 2.7.4
>> >>

  reply	other threads:[~2019-12-09 16:58 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 ` [PATCH v2 1/2] thermal: armada: fix register offsets for AXP 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 [this message]
2019-12-09 17:11           ` Daniel Lezcano
     [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=BN8PR10MB337975A77D726FDAFA9F13598C580@BN8PR10MB3379.namprd10.prod.outlook.com \
    --to=zak.hays@lexmark.com \
    --cc=amit.kucheria@verdurent.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=rui.zhang@intel.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;
as well as URLs for NNTP newsgroup(s).