From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Nishanth Menon <nm@ti.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Dave Gerlach <d-gerlach@ti.com>, Tony Lindgren <tony@atomide.com>,
Linux PM <linux-pm@vger.kernel.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Lukasz Majewski <lukma@denx.de>, Rob Herring <robh+dt@kernel.org>,
Linux OMAP Mailing List <linux-omap@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v6 2/4] Documentation: dt: add bindings for ti-cpufreq
Date: Fri, 10 Feb 2017 13:28 +0100 [thread overview]
Message-ID: <3046998.7dExGlRDb3@aspire.rjw.lan> (raw)
In-Reply-To: <20170210031349.GG14503@vireshk-i7>
On Friday, February 10, 2017 08:43:49 AM Viresh Kumar wrote:
> On 09-02-17, 23:03, Rafael J. Wysocki wrote:
> > In particular, Viresh, if you ACK something, please make sure that it
> > doesn't conflict with your own patches.
>
> I hope you are talking about the patch 3/4 for which Arnd also sent a
> fix. I acked it back on 18th of January and Dave has been carrying my
> Ack since then. When he posted again, I didn't went into reviewing it
> again as I saw my Ack being there.
Well, OK, but you did know that the OPP API had changed in the meantime,
so it wouldn't have hurt to double check I suppose?
> Yes, he ended up using an API which just got updated after 18th of Jan
> and yes both me and Dave missed that. But I feel it is difficult to
> take care of scenarios like this. Perhaps he should have made sure
> that he base it of pm/linux-next and nothing would have gone wrong.
Yes, that would help, but then how to enforce that?
Thanks,
Rafael
next prev parent reply other threads:[~2017-02-10 12:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-03 17:29 [PATCH v5 0/4] cpufreq: Introduce TI CPUFreq/OPP Driver Dave Gerlach
[not found] ` <20170203172929.23940-1-d-gerlach-l0cyMroinI0@public.gmane.org>
2017-02-03 17:29 ` [PATCH v5 1/4] PM / OPP: Expose _of_get_opp_desc_node as dev_pm_opp API Dave Gerlach
2017-02-03 17:29 ` [PATCH v5 3/4] cpufreq: ti: Add cpufreq driver to determine available OPPs at runtime Dave Gerlach
2017-02-03 17:29 ` [PATCH v5 2/4] Documentation: dt: add bindings for ti-cpufreq Dave Gerlach
2017-02-08 14:44 ` Rob Herring
2017-02-08 14:45 ` Dave Gerlach
2017-02-09 0:02 ` Rafael J. Wysocki
2017-02-09 15:36 ` Dave Gerlach
2017-02-09 15:35 ` [PATCH v6 " Dave Gerlach
2017-02-09 16:01 ` Rob Herring
2017-02-09 22:03 ` Rafael J. Wysocki
2017-02-10 3:13 ` Viresh Kumar
2017-02-10 12:28 ` Rafael J. Wysocki [this message]
[not found] ` <3046998.7dExGlRDb3-yvgW3jdyMHm1GS7QM15AGw@public.gmane.org>
2017-02-10 20:55 ` Dave Gerlach
2017-02-03 17:29 ` [PATCH v5 4/4] cpufreq: dt: Don't use generic platdev driver for ti-cpufreq platforms Dave Gerlach
2017-02-03 23:23 ` [PATCH v5 0/4] cpufreq: Introduce TI CPUFreq/OPP Driver Lukasz Majewski
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=3046998.7dExGlRDb3@aspire.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=d-gerlach@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukma@denx.de \
--cc=nm@ti.com \
--cc=rafael@kernel.org \
--cc=robh+dt@kernel.org \
--cc=tony@atomide.com \
--cc=viresh.kumar@linaro.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;
as well as URLs for NNTP newsgroup(s).