All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chanwoo Choi <cw00.choi@samsung.com>
To: myungjoo.ham@samsung.com
Cc: linux-pm@vger.kernel.org, kyungmin.park@samsung.com,
	rjw@rjwysocki.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/4] PM / devfreq: Update the devfreq and devfreq-event device
Date: Mon, 23 Jan 2017 09:29:36 +0900	[thread overview]
Message-ID: <58854E70.7040600@samsung.com> (raw)
In-Reply-To: <1484569567-29810-1-git-send-email-cw00.choi@samsung.com>

Ping. Hi Myungjoo,

Could you apply these patches if there is no any comment?


On 2017년 01월 16일 21:26, Chanwoo Choi wrote:
> This patches update the devfreq and devfreq-event device. I add the summary
> of each patch as following.
> - Patch1 fixes the wrong description of governor_userspace.c.
> - Patch2 show the information of registered PPMU devices.
> - Patch3/4 modify the name of sysfs entry for devfreq/devfreq-event device
> 
> Changes from v2:
> (https://lkml.org/lkml/2016/12/28/102)
> - On v2 patchset, patch1/2/3/5 were merged on devfreq git repo.
> - Remain the warning message for exynos-ppmu.c when failed to get the clock of ppmu
> - Rebase these patches on devfreq git repo[1].
> 
> Changes from v1:
> - Rebase these patches on v4.10-rc1.
> - Include the separate patch[2] in these patches.
> 
> [1] https://git.kernel.org/cgit/linux/kernel/git/mzx/devfreq.git/ (branch: for-4.10-rc)
> [2] https://lkml.org/lkml/2016/12/16/7
> - [PATCH] PM / devfreq: Fix the wrong description for userspace governor
> 
> Chanwoo Choi (4):
>   PM / devfreq: Fix the wrong description for userspace governor
>   PM / devfreq: exynos-ppmu: Show the registred device for ppmu device
>   PM / devfreq: Simplify the sysfs name of devfreq-event device
>   PM / devfreq: Modify the device name as devfreq[X] for sysfs
> 
>  drivers/devfreq/devfreq-event.c      | 2 +-
>  drivers/devfreq/devfreq.c            | 4 +++-
>  drivers/devfreq/event/exynos-ppmu.c  | 3 +++
>  drivers/devfreq/governor_userspace.c | 3 +--
>  4 files changed, 8 insertions(+), 4 deletions(-)
> 


-- 
Best Regards,
Chanwoo Choi
S/W R&D Center
Samsung Electronics

  parent reply	other threads:[~2017-01-23  0:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20170116122609epcas5p34b6109202b5bc05f13325318d0f2dbe3@epcas5p3.samsung.com>
2017-01-16 12:26 ` [PATCH v3 0/4] PM / devfreq: Update the devfreq and devfreq-event device Chanwoo Choi
2017-01-16 12:26   ` [PATCH v3 1/4] PM / devfreq: Fix the wrong description for userspace governor Chanwoo Choi
2017-01-16 12:26   ` [PATCH v3 2/4] PM / devfreq: exynos-ppmu: Show the registred device for ppmu device Chanwoo Choi
2017-01-16 12:26     ` Chanwoo Choi
2017-01-16 12:26   ` [PATCH v3 3/4] PM / devfreq: Simplify the sysfs name of devfreq-event device Chanwoo Choi
2017-01-16 12:26   ` [PATCH v3 4/4] PM / devfreq: Modify the device name as devfreq[X] for sysfs Chanwoo Choi
2017-01-23  0:29   ` Chanwoo Choi [this message]
     [not found]   ` <CGME20170116122609epcas5p3e9f106e6d097613cd866107bc0e065c7@epcas5p3.samsung.com>
2017-01-23  2:19     ` MyungJoo Ham
2017-01-23  3:25       ` Chanwoo Choi

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=58854E70.7040600@samsung.com \
    --to=cw00.choi@samsung.com \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=myungjoo.ham@samsung.com \
    --cc=rjw@rjwysocki.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.