All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chanwoo Choi <cw00.choi@samsung.com>
To: Rob Herring <robh@kernel.org>
Cc: MyungJoo Ham <myungjoo.ham@samsung.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Kyungmin Park <kyungmin.park@samsung.com>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>
Subject: Re: [PATCH] devfreq: Convert to using %pOF instead of full_name
Date: Fri, 25 Aug 2017 10:26:32 +0900	[thread overview]
Message-ID: <599F7CC8.1040406@samsung.com> (raw)
In-Reply-To: <CAL_Jsq+LW8ZmE_J0B9Cea_Y0iDkBX46cXWnAF882C9-7SB_T=A@mail.gmail.com>

On 2017년 08월 24일 23:23, Rob Herring wrote:
> On Wed, Aug 23, 2017 at 6:18 PM, Chanwoo Choi <cw00.choi@samsung.com> wrote:
>> Hi Rob,
>>
>> On 2017년 08월 24일 03:09, Rob Herring wrote:
>>> On Thu, Jul 20, 2017 at 12:25 AM, MyungJoo Ham <myungjoo.ham@samsung.com> wrote:
>>>>> On 2017년 07월 19일 06:42, Rob Herring wrote:
>>>>>> Now that we have a custom printf format specifier, convert users of
>>>>>> full_name to use %pOF instead. This is preparation to remove storing
>>>>>> of the full path string for each node.
>>>>>>
>>>>>> Signed-off-by: Rob Herring <robh@kernel.org>
>>>>>> Cc: Chanwoo Choi <cw00.choi@samsung.com>
>>>>>> Cc: MyungJoo Ham <myungjoo.ham@samsung.com>
>>>>>> Cc: Kyungmin Park <kyungmin.park@samsung.com>
>>>>>> Cc: linux-pm@vger.kernel.org
>>>>>> ---
>>>>>>  drivers/devfreq/devfreq-event.c | 4 ++--
>>>>>>  1 file changed, 2 insertions(+), 2 deletions(-)
>>>>>>
>>>>>> diff --git a/drivers/devfreq/devfreq-event.c b/drivers/devfreq/devfreq-event.c
>>>>>> index 8648b32ebc89..d67242d87744 100644
>>>>>> --- a/drivers/devfreq/devfreq-event.c
>>>>>> +++ b/drivers/devfreq/devfreq-event.c
>>>>>> @@ -277,8 +277,8 @@ int devfreq_event_get_edev_count(struct device *dev)
>>>>>>                                             sizeof(u32));
>>>>>>     if (count < 0) {
>>>>>>             dev_err(dev,
>>>>>> -                   "failed to get the count of devfreq-event in %s node\n",
>>>>>> -                   dev->of_node->full_name);
>>>>>> +                   "failed to get the count of devfreq-event in %pOF node\n",
>>>>>> +                   dev->of_node);
>>>>>>             return count;
>>>>>>     }
>>>>>>
>>>>>
>>>>> Reviewed-by: Chanwoo Choi <cw00.choi@samsung.com>
>>>>>
>>>>
>>>> Acked-by: MyungJoo Ham <myungjoo.ham@samsung.com>
>>>
>>> Please take this thru the devfreq tree.
>>
>> This patch was merged on devfreq tree.
>> https://git.kernel.org/pub/scm/linux/kernel/git/mzx/devfreq.git/commit/?h=for-next&id=7f46535e8a2e3c3e415e55eaadcb9d9a153a5300
> 
> Okay, it's not showing up in linux-next which is why I asked.

As I knew, devfreq maintainer has not yet asked
the inclusion of devfreq tree in linux-next.

To Myungjoo,
You can ask to 'Stephen Rothwell <sfr@canb.auug.org.au>'
for the inclusion of devfreq tree in linux-next.

git://git.kernel.org/pub/scm/linux/kernel/git/mzx/devfreq.git for-next

-- 
Best Regards,
Chanwoo Choi
Samsung Electronics

      reply	other threads:[~2017-08-25  1:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20170718214411epcas2p43fc1475c80245889737ba9e731497e38@epcas2p4.samsung.com>
2017-07-18 21:42 ` [PATCH] devfreq: Convert to using %pOF instead of full_name Rob Herring
2017-07-19  1:38   ` Chanwoo Choi
     [not found]   ` <CGME20170718214411epcas2p43fc1475c80245889737ba9e731497e38@epcms1p2>
2017-07-20  5:25     ` MyungJoo Ham
2017-07-20  5:25       ` MyungJoo Ham
2017-08-23 18:09       ` Rob Herring
2017-08-23 18:09         ` Rob Herring
2017-08-23 23:18         ` Chanwoo Choi
2017-08-24 14:23           ` Rob Herring
2017-08-25  1:26             ` Chanwoo Choi [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=599F7CC8.1040406@samsung.com \
    --to=cw00.choi@samsung.com \
    --cc=devicetree@vger.kernel.org \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=myungjoo.ham@samsung.com \
    --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 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.