From: Dave Gerlach <d-gerlach-l0cyMroinI0@public.gmane.org> To: "Rafael J. Wysocki" <rjw-LthD3rsA81gm4RdzfppkhA@public.gmane.org>, Viresh Kumar <viresh.kumar-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org> Cc: "Rafael J. Wysocki" <rafael-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>, Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>, Tony Lindgren <tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>, "linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org" <linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>, Linux OMAP Mailing List <linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>, Linux PM <linux-pm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>, "devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" <devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>, Nishanth Menon <nm-l0cyMroinI0@public.gmane.org>, Lukasz Majewski <lukma-ynQEQJNshbs@public.gmane.org> Subject: Re: [PATCH v6 2/4] Documentation: dt: add bindings for ti-cpufreq Date: Fri, 10 Feb 2017 14:55:29 -0600 [thread overview] Message-ID: <4af419d0-9730-756f-916d-88e07e704448@ti.com> (raw) In-Reply-To: <3046998.7dExGlRDb3-yvgW3jdyMHm1GS7QM15AGw@public.gmane.org> On 02/10/2017 06:28 AM, Rafael J. Wysocki wrote: > 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? I apologize, I was unaware of the conflicting series. I'm not sure of a good way to enforce it but I do agree I will make sure to rebase and test against pm/linux-next before sending in the future. Regards, Dave > > 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
WARNING: multiple messages have this Message-ID (diff)
From: d-gerlach@ti.com (Dave Gerlach) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH v6 2/4] Documentation: dt: add bindings for ti-cpufreq Date: Fri, 10 Feb 2017 14:55:29 -0600 [thread overview] Message-ID: <4af419d0-9730-756f-916d-88e07e704448@ti.com> (raw) In-Reply-To: <3046998.7dExGlRDb3@aspire.rjw.lan> On 02/10/2017 06:28 AM, Rafael J. Wysocki wrote: > 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? I apologize, I was unaware of the conflicting series. I'm not sure of a good way to enforce it but I do agree I will make sure to rebase and test against pm/linux-next before sending in the future. Regards, Dave > > Thanks, > Rafael >
next prev parent reply other threads:[~2017-02-10 20:55 UTC|newest] Thread overview: 32+ 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 2017-02-03 17:29 ` 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 ` 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 ` Dave Gerlach 2017-02-03 17:29 ` [PATCH v5 2/4] Documentation: dt: add bindings for ti-cpufreq Dave Gerlach 2017-02-03 17:29 ` Dave Gerlach 2017-02-08 14:44 ` Rob Herring 2017-02-08 14:44 ` Rob Herring 2017-02-08 14:45 ` Dave Gerlach 2017-02-08 14:45 ` Dave Gerlach 2017-02-09 0:02 ` Rafael J. Wysocki 2017-02-09 0:02 ` Rafael J. Wysocki 2017-02-09 15:36 ` Dave Gerlach 2017-02-09 15:36 ` Dave Gerlach 2017-02-09 15:35 ` [PATCH v6 " Dave Gerlach 2017-02-09 15:35 ` Dave Gerlach 2017-02-09 16:01 ` Rob Herring 2017-02-09 16:01 ` Rob Herring 2017-02-09 22:03 ` Rafael J. Wysocki 2017-02-09 22:03 ` Rafael J. Wysocki 2017-02-10 3:13 ` Viresh Kumar 2017-02-10 3:13 ` Viresh Kumar 2017-02-10 12:28 ` Rafael J. Wysocki 2017-02-10 12:28 ` Rafael J. Wysocki [not found] ` <3046998.7dExGlRDb3-yvgW3jdyMHm1GS7QM15AGw@public.gmane.org> 2017-02-10 20:55 ` Dave Gerlach [this message] 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 17:29 ` Dave Gerlach 2017-02-03 23:23 ` [PATCH v5 0/4] cpufreq: Introduce TI CPUFreq/OPP Driver Lukasz Majewski 2017-02-03 23:23 ` 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=4af419d0-9730-756f-916d-88e07e704448@ti.com \ --to=d-gerlach-l0cymroini0@public.gmane.org \ --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \ --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \ --cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \ --cc=linux-pm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \ --cc=lukma-ynQEQJNshbs@public.gmane.org \ --cc=nm-l0cyMroinI0@public.gmane.org \ --cc=rafael-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \ --cc=rjw-LthD3rsA81gm4RdzfppkhA@public.gmane.org \ --cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \ --cc=tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org \ --cc=viresh.kumar-QSEj5FYQhm4dnm+yROfE0A@public.gmane.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: linkBe 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.