mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chanwoo Choi <cw00.choi@samsung.com>
To: myungjoo.ham@samsung.com, kyungmin.park@samsung.com
Cc: rjw@rjwysocki.net, subhashj@codeaurora.org,
	linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
	Chanwoo Choi <cw00.choi@samsung.com>
Subject: [PATCH v2 0/2] PM / devfreq: Use the resource-managed function for devfreq device
Date: Tue, 08 Nov 2016 18:13:26 +0900	[thread overview]
Message-ID: <1478596408-2958-1-git-send-email-cw00.choi@samsung.com> (raw)

This patch just uses the resource-managed function when adding the new devfreq
deivce. This function handles the memory and delete of devfreq instance
automatically.

Changes from v1:
- Rebased these patches on linux-next (20161108)

Chanwoo Choi (2):
  PM / devfreq: rk3399_dmc: Use the resource-managed function to add devfreq dev
  scsi: ufs: Use the resource-managed function to add devfreq device

 drivers/devfreq/rk3399_dmc.c | 2 +-
 drivers/scsi/ufs/ufshcd.c    | 4 +---
 2 files changed, 2 insertions(+), 4 deletions(-)

-- 
1.9.1

             reply	other threads:[~2016-11-08  9:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-08  9:13 Chanwoo Choi [this message]
2016-11-08  9:13 ` [PATCH v2 1/2] PM / devfreq: rk3399_dmc: Use the resource-managed function to add devfreq dev Chanwoo Choi
2016-11-08  9:13 ` [PATCH v2 2/2] scsi: ufs: Use the resource-managed function to add devfreq device Chanwoo Choi
2016-11-09  0:17   ` Martin K. Petersen
2016-11-08  9:16 ` Chanwoo Choi
2016-11-08 20:40   ` Subhash Jadavani
     [not found] ` <CGME20161108091331epcas1p252b29eaa3bdd280c9b44c3d1da4d12ca@epcas1p2.samsung.com>
2016-11-09  1:20   ` [PATCH v2 1/2] PM / devfreq: rk3399_dmc: Use the resource-managed function to add devfreq dev MyungJoo Ham
     [not found] ` <CGME20161108091702epcas5p4779c47d7341e22697e7e49dd2f91ae0b@epcas5p4.samsung.com>
2016-11-09  1:26   ` [PATCH v2 2/2] scsi: ufs: Use the resource-managed function to add devfreq device MyungJoo Ham

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=1478596408-2958-1-git-send-email-cw00.choi@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 \
    --cc=subhashj@codeaurora.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
all inboxes | Powered by JetHome®