public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chanwoo Choi <cw00.choi@samsung.com>
To: linux-kernel@vger.kernel.org, myungjoo.ham@samsung.com,
	rjw@rjwysocki.net, gregkh@linuxfoundation.org
Cc: chanwoo@kernel.org, mchehab+samsung@kernel.org,
	davem@davemloft.net, robh@kernel.org, paulmck@linux.ibm.com,
	cpgs@samsung.com, Chanwoo Choi <cw00.choi@samsung.com>
Subject: [PATCH] MAINTAINERS: Update myself as maintainer for DEVFREQ subsystem support
Date: Tue,  5 Nov 2019 14:41:19 +0900	[thread overview]
Message-ID: <1019298652.01572934681167.JavaMail.epsvc@epcpadp2> (raw)
In-Reply-To: CGME20191105053547epcas1p248c5a77579a8dd6fbd3639a12f3ca4c5@epcas1p2.samsung.com

Update myself to the DEVFREQ entry as maintainer from reviewer and
the git repository information to manage the devfreq patches. I've been
reviewing and tesing the devfreq support for the couple of years as reviewer.
From now, I'll help and reiview the devfreq as maintainer.

Suggested-by: MyungJoo Ham <myungjoo.ham@samsung.com>
Signed-off-by: Chanwoo Choi <cw00.choi@samsung.com>
---
 MAINTAINERS | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/MAINTAINERS b/MAINTAINERS
index cba1095547fd..ebc1078c1ecb 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -3532,7 +3532,7 @@ BUS FREQUENCY DRIVER FOR SAMSUNG EXYNOS
 M:	Chanwoo Choi <cw00.choi@samsung.com>
 L:	linux-pm@vger.kernel.org
 L:	linux-samsung-soc@vger.kernel.org
-T:	git git://git.kernel.org/pub/scm/linux/kernel/git/mzx/devfreq.git
+T:	git git://git.kernel.org/pub/scm/linux/kernel/git/chanwoo/linux.git
 S:	Maintained
 F:	drivers/devfreq/exynos-bus.c
 F:	Documentation/devicetree/bindings/devfreq/exynos-bus.txt
@@ -4762,9 +4762,9 @@ F:	include/linux/devcoredump.h
 DEVICE FREQUENCY (DEVFREQ)
 M:	MyungJoo Ham <myungjoo.ham@samsung.com>
 M:	Kyungmin Park <kyungmin.park@samsung.com>
-R:	Chanwoo Choi <cw00.choi@samsung.com>
+M:	Chanwoo Choi <cw00.choi@samsung.com>
 L:	linux-pm@vger.kernel.org
-T:	git git://git.kernel.org/pub/scm/linux/kernel/git/mzx/devfreq.git
+T:	git git://git.kernel.org/pub/scm/linux/kernel/git/chanwoo/linux.git
 S:	Maintained
 F:	drivers/devfreq/
 F:	include/linux/devfreq.h
@@ -4774,7 +4774,7 @@ F:	include/trace/events/devfreq.h
 DEVICE FREQUENCY EVENT (DEVFREQ-EVENT)
 M:	Chanwoo Choi <cw00.choi@samsung.com>
 L:	linux-pm@vger.kernel.org
-T:	git git://git.kernel.org/pub/scm/linux/kernel/git/mzx/devfreq.git
+T:	git git://git.kernel.org/pub/scm/linux/kernel/git/chanwoo/linux.git
 S:	Supported
 F:	drivers/devfreq/event/
 F:	drivers/devfreq/devfreq-event.c
-- 
2.17.1



       reply	other threads:[~2019-11-05  6:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20191105053547epcas1p248c5a77579a8dd6fbd3639a12f3ca4c5@epcas1p2.samsung.com>
2019-11-05  5:41 ` Chanwoo Choi [this message]
2019-11-05  7:35   ` [PATCH] MAINTAINERS: Update myself as maintainer for DEVFREQ subsystem support MyungJoo Ham
2019-11-05 16:44     ` Rafael J. Wysocki
2019-11-06  2:59       ` Chanwoo Choi
2019-11-06 10:47         ` Rafael J. Wysocki

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=1019298652.01572934681167.JavaMail.epsvc@epcpadp2 \
    --to=cw00.choi@samsung.com \
    --cc=chanwoo@kernel.org \
    --cc=cpgs@samsung.com \
    --cc=davem@davemloft.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab+samsung@kernel.org \
    --cc=myungjoo.ham@samsung.com \
    --cc=paulmck@linux.ibm.com \
    --cc=rjw@rjwysocki.net \
    --cc=robh@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