From: Dmitry Osipenko <digetx@gmail.com>
To: Stephen Boyd <sboyd@kernel.org>,
Peter De Schrijver <pdeschrijver@nvidia.com>
Cc: Prashant Gaikwad <pgaikwad@nvidia.com>,
Michael Turquette <mturquette@baylibre.com>,
Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
linux-clk@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 0/2] clk: Tegra124 PLLM fixes
Date: Thu, 25 Apr 2019 18:43:13 +0300 [thread overview]
Message-ID: <692c6b3f-9f46-0b0a-63a7-029ec7a7409d@gmail.com> (raw)
In-Reply-To: <155620524950.15276.14252541417126056267@swboyd.mtv.corp.google.com>
25.04.2019 18:14, Stephen Boyd пишет:
> Quoting Dmitry Osipenko (2019-04-25 06:50:39)
>> 24.04.2019 11:36, Peter De Schrijver пишет:
>>> On Fri, Apr 19, 2019 at 02:50:10PM +0300, Dmitry Osipenko wrote:
>>>> 12.04.2019 0:48, Dmitry Osipenko пишет:
>>>>
>>>> The patches in this series are trivial and fixing the longstanding bug on Tegra124. Could you please take a look and and ACK the series if it looks good to you?
>>>
>>> Acked-By: Peter De Schrijver <pdeschrijver@nvidia.com>
>>
>> Thank you, Peter.
>>
>>
>> Stephen, is yours maintainer-tool able to pick up the "Acked-By" for the whole series or do I need to resend the series with a proper "Acked-by" tag added to every patch? Please let me know.
>
> The maintainer-tool is me, but I don't require you to resend to collect
> acks or other tags. I can do it and I'll do it today.
>
Thank you very much!
prev parent reply other threads:[~2019-04-25 15:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-11 21:48 Dmitry Osipenko
2019-04-11 21:48 ` [PATCH v1 1/2] clk: tegra: Fix PLLM programming on Tegra124+ when PMC overrides divider Dmitry Osipenko
2019-04-25 15:17 ` Stephen Boyd
2019-04-11 21:48 ` [PATCH v1 2/2] clk: tegra124: Remove lock-enable bit from PLLM Dmitry Osipenko
2019-04-25 15:17 ` Stephen Boyd
2019-04-19 11:50 ` [PATCH v1 0/2] clk: Tegra124 PLLM fixes Dmitry Osipenko
2019-04-24 8:36 ` Peter De Schrijver
2019-04-25 13:50 ` Dmitry Osipenko
2019-04-25 15:14 ` Stephen Boyd
2019-04-25 15:43 ` Dmitry Osipenko [this message]
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=692c6b3f-9f46-0b0a-63a7-029ec7a7409d@gmail.com \
--to=digetx@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=pdeschrijver@nvidia.com \
--cc=pgaikwad@nvidia.com \
--cc=sboyd@kernel.org \
--cc=thierry.reding@gmail.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®