From: Dmitry Osipenko <digetx@gmail.com>
To: "Chanwoo Choi" <cw00.choi@samsung.com>,
"Thierry Reding" <thierry.reding@gmail.com>,
"MyungJoo Ham" <myungjoo.ham@samsung.com>,
"Kyungmin Park" <kyungmin.park@samsung.com>,
"Jonathan Hunter" <jonathanh@nvidia.com>,
"Tomeu Vizoso" <tomeu.vizoso@collabora.com>,
"Peter Geis" <pgwipeout@gmail.com>,
"Michał Mirosław" <mirq-linux@rere.qmqm.pl>
Cc: linux-pm@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v9 19/19] PM / devfreq: tegra20/30: Add Dmitry as a maintainer
Date: Tue, 5 Nov 2019 16:29:31 +0300 [thread overview]
Message-ID: <9bd7bfc0-508f-e7fb-d985-d32f2d9a88d8@gmail.com> (raw)
In-Reply-To: <0e7db72b-37ff-a36e-11fe-727ed43c26a6@samsung.com>
05.11.2019 07:07, Chanwoo Choi пишет:
> On 19. 11. 5. 오전 6:56, Dmitry Osipenko wrote:
>> I was contributing to the NVIDIA Tegra20+ devfreq drivers recently and
>> want to help keep them working and evolving in the future.
>>
>> Acked-by: Chanwoo Choi <cw00.choi@samsung.com>
>> Signed-off-by: Dmitry Osipenko <digetx@gmail.com>
>> ---
>> MAINTAINERS | 9 +++++++++
>> 1 file changed, 9 insertions(+)
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index 9f69d01da3a6..4b9679988514 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -10632,6 +10632,15 @@ F: include/linux/memblock.h
>> F: mm/memblock.c
>> F: Documentation/core-api/boot-time-mm.rst
>>
>> +MEMORY FREQUENCY SCALING DRIVERS FOR NVIDIA TEGRA
>> +M: Dmitry Osipenko <digetx@gmail.com>
>> +L: linux-pm@vger.kernel.org
>> +L: linux-tegra@vger.kernel.org
>> +T: git git://git.kernel.org/pub/scm/linux/kernel/git/mzx/devfreq.git
>> +S: Maintained
>> +F: drivers/devfreq/tegra20-devfreq.c
>> +F: drivers/devfreq/tegra30-devfreq.c
>> +
>> MEMORY MANAGEMENT
>> L: linux-mm@kvack.org
>> W: https://protect2.fireeye.com/url?k=9d0ba644-c09508de-9d0a2d0b-0cc47a336fae-300ed90f1ba3077c&u=http://www.linux-mm.org/
>>
>
> Looks good to me.
>
> But, the merge conflict might be occurred.
> After getting the review from Myungjoo,
> you better to send this patch separately
> based on the latest MAINTAINERS file.
>
> Thanks for your all efforts.
Okay, I'll wait for the rest of patches to land and then re-send this
patch separately. Thank you very much for the reviews.
next prev parent reply other threads:[~2019-11-05 13:29 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-04 21:55 [PATCH v9 00/19] More improvements for Tegra30 devfreq driver Dmitry Osipenko
2019-11-04 21:55 ` [PATCH v9 01/19] PM / devfreq: tegra30: Change irq type to unsigned int Dmitry Osipenko
2019-11-04 21:56 ` [PATCH v9 02/19] PM / devfreq: tegra30: Keep interrupt disabled while governor is stopped Dmitry Osipenko
2019-11-04 21:56 ` [PATCH v9 03/19] PM / devfreq: tegra30: Handle possible round-rate error Dmitry Osipenko
2019-11-04 21:56 ` [PATCH v9 04/19] PM / devfreq: tegra30: Drop write-barrier Dmitry Osipenko
2019-11-04 21:56 ` [PATCH v9 05/19] PM / devfreq: tegra30: Fix integer overflow on CPU's freq max out Dmitry Osipenko
2019-11-04 21:56 ` [PATCH v9 06/19] PM / devfreq: tegra30: Use kHz units uniformly in the code Dmitry Osipenko
2019-11-04 21:56 ` [PATCH v9 07/19] PM / devfreq: tegra30: Use CPUFreq notifier Dmitry Osipenko
2019-11-04 21:56 ` [PATCH v9 08/19] PM / devfreq: tegra30: Move clk-notifier's registration to governor's start Dmitry Osipenko
2019-11-04 21:56 ` [PATCH v9 09/19] PM / devfreq: tegra30: Reset boosting on startup Dmitry Osipenko
2019-11-04 21:56 ` [PATCH v9 10/19] PM / devfreq: tegra30: Don't enable consecutive-down interrupt " Dmitry Osipenko
2019-11-04 21:56 ` [PATCH v9 11/19] PM / devfreq: tegra30: Constify structs Dmitry Osipenko
2019-11-04 21:56 ` [PATCH v9 12/19] PM / devfreq: tegra30: Include appropriate header Dmitry Osipenko
2019-11-04 21:56 ` [PATCH v9 13/19] PM / devfreq: tegra30: Don't enable already enabled consecutive interrupts Dmitry Osipenko
2019-11-04 21:56 ` [PATCH v9 14/19] PM / devfreq: tegra30: Disable consecutive interrupts when appropriate Dmitry Osipenko
2019-11-04 21:56 ` [PATCH v9 15/19] PM / devfreq: tegra30: Use kHz units for dependency threshold Dmitry Osipenko
2019-11-05 4:02 ` Chanwoo Choi
2019-11-04 21:56 ` [PATCH v9 16/19] PM / devfreq: Add new interrupt_driven flag for governors Dmitry Osipenko
2019-11-05 4:01 ` Chanwoo Choi
2019-11-04 21:56 ` [PATCH v9 17/19] PM / devfreq: tegra30: Support variable polling interval Dmitry Osipenko
2019-11-05 4:02 ` Chanwoo Choi
2019-11-04 21:56 ` [PATCH v9 18/19] PM / devfreq: tegra30: Tune up MCCPU boost-down coefficient Dmitry Osipenko
2019-11-04 21:56 ` [PATCH v9 19/19] PM / devfreq: tegra20/30: Add Dmitry as a maintainer Dmitry Osipenko
2019-11-05 4:07 ` Chanwoo Choi
2019-11-05 13:29 ` Dmitry Osipenko [this message]
2019-11-06 1:24 ` Chanwoo Choi
2019-11-06 16:14 ` Dmitry Osipenko
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=9bd7bfc0-508f-e7fb-d985-d32f2d9a88d8@gmail.com \
--to=digetx@gmail.com \
--cc=cw00.choi@samsung.com \
--cc=jonathanh@nvidia.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mirq-linux@rere.qmqm.pl \
--cc=myungjoo.ham@samsung.com \
--cc=pgwipeout@gmail.com \
--cc=thierry.reding@gmail.com \
--cc=tomeu.vizoso@collabora.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).