All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Rob Herring <robh@kernel.org>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Daniel Lezcano <daniel.lezcano@linaro.org>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>
Subject: Re: [PATCH] cpuidle: Convert to using %pOF instead of full_name
Date: Wed, 23 Aug 2017 22:53:35 +0200	[thread overview]
Message-ID: <14600557.ytcEGHVfm3@aspire.rjw.lan> (raw)
In-Reply-To: <CABGGisxq7jQh+7etb8RnThTkQ09Svmz6+D3Bwqx9yQUOihoVQA@mail.gmail.com>

On Wednesday, August 23, 2017 10:49:00 PM CEST Rob Herring wrote:
> On Wed, Aug 23, 2017 at 3:34 PM, Rafael J. Wysocki <rafael@kernel.org> wrote:
> > On Wed, Aug 23, 2017 at 8:14 PM, Rob Herring <robh@kernel.org> wrote:
> >> On Tue, Jul 18, 2017 at 4:42 PM, Rob Herring <robh@kernel.org> 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: "Rafael J. Wysocki" <rjw@rjwysocki.net>
> >>> Cc: Daniel Lezcano <daniel.lezcano@linaro.org>
> >>> Cc: linux-pm@vger.kernel.org
> >>> ---
> >>>  drivers/cpuidle/dt_idle_states.c | 20 ++++++++++----------
> >>>  1 file changed, 10 insertions(+), 10 deletions(-)
> >>
> >> Rafael, Ping. Please apply this one and 2 others for cpufreq and
> >> PM-domains which haven't been applied yet.
> >
> > I thought that these would go in through the DT tree.
> >
> > I'll try to find them, but next time please make it clear how you want
> > to route things.
> 
> Sorry, I thought addressed TO you and not in a series was enough to imply that.

Well, Patchwork doesn't tell me who the patch was addressed to. :-)

Thanks,
Rafael

WARNING: multiple messages have this Message-ID (diff)
From: "Rafael J. Wysocki" <rjw-LthD3rsA81gm4RdzfppkhA@public.gmane.org>
To: Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: "Rafael J. Wysocki"
	<rafael-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Daniel Lezcano
	<daniel.lezcano-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
	"linux-pm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-pm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH] cpuidle: Convert to using %pOF instead of full_name
Date: Wed, 23 Aug 2017 22:53:35 +0200	[thread overview]
Message-ID: <14600557.ytcEGHVfm3@aspire.rjw.lan> (raw)
In-Reply-To: <CABGGisxq7jQh+7etb8RnThTkQ09Svmz6+D3Bwqx9yQUOihoVQA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On Wednesday, August 23, 2017 10:49:00 PM CEST Rob Herring wrote:
> On Wed, Aug 23, 2017 at 3:34 PM, Rafael J. Wysocki <rafael-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> wrote:
> > On Wed, Aug 23, 2017 at 8:14 PM, Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> wrote:
> >> On Tue, Jul 18, 2017 at 4:42 PM, Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> 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-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
> >>> Cc: "Rafael J. Wysocki" <rjw-LthD3rsA81gm4RdzfppkhA@public.gmane.org>
> >>> Cc: Daniel Lezcano <daniel.lezcano-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
> >>> Cc: linux-pm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> >>> ---
> >>>  drivers/cpuidle/dt_idle_states.c | 20 ++++++++++----------
> >>>  1 file changed, 10 insertions(+), 10 deletions(-)
> >>
> >> Rafael, Ping. Please apply this one and 2 others for cpufreq and
> >> PM-domains which haven't been applied yet.
> >
> > I thought that these would go in through the DT tree.
> >
> > I'll try to find them, but next time please make it clear how you want
> > to route things.
> 
> Sorry, I thought addressed TO you and not in a series was enough to imply that.

Well, Patchwork doesn't tell me who the patch was addressed to. :-)

Thanks,
Rafael

--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2017-08-23 21:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-18 21:42 [PATCH] cpuidle: Convert to using %pOF instead of full_name Rob Herring
2017-08-23 18:14 ` Rob Herring
2017-08-23 18:14   ` Rob Herring
2017-08-23 20:34   ` Rafael J. Wysocki
2017-08-23 20:49     ` Rob Herring
2017-08-23 20:49       ` Rob Herring
2017-08-23 20:53       ` Rafael J. Wysocki [this message]
2017-08-23 20:53         ` 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=14600557.ytcEGHVfm3@aspire.rjw.lan \
    --to=rjw@rjwysocki.net \
    --cc=daniel.lezcano@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rafael@kernel.org \
    --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.