All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Mason <slash.tmp@free.fr>
Cc: "Viresh Kumar" <viresh.kumar@linaro.org>,
	mmcclint@codeaurora.org, "Rafael Wysocki" <rjw@rjwysocki.net>,
	"Arnd Bergmann" <arnd.bergmann@linaro.org>,
	"Lists linaro-kernel" <linaro-kernel@lists.linaro.org>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	"Kukjin Kim" <kgene.kim@samsung.com>,
	xf@rock-chips.com, "Heiko Stübner" <heiko@sntech.de>,
	"Krzysztof Kozłowski" <k.kozlowski@samsung.com>
Subject: Re: [PATCH V3 0/4] cpufreq: dt: Create platform device from generic code
Date: Thu, 21 Apr 2016 00:31:25 +0200	[thread overview]
Message-ID: <CAJZ5v0h0T=XyC2bd3RByAC7mSYqRRcTe9XDVULHRz0Owr3a9Kg@mail.gmail.com> (raw)
In-Reply-To: <5717F43D.1060504@free.fr>

On Wed, Apr 20, 2016 at 11:27 PM, Mason <slash.tmp@free.fr> wrote:
> On 20/04/2016 11:55, Viresh Kumar wrote:
>> On 30-03-16, 13:45, Viresh Kumar wrote:
>>> Multiple platforms are using the generic cpufreq-dt driver now, and all
>>> of them are required to create a platform device with name "cpufreq-dt",
>>> in order to get the cpufreq-dt probed.
>>>
>>> Many of them do it from platform code, others have special drivers just
>>> to do that.
>>>
>>> It would be more sensible to do this at a generic place, where all such
>>> platform can mark their entries.
>>>
>>> The first patch fixes an issue that came up with an earlier version of
>>> patch 2/4, but its still worth fixing it.  The second one creates a new
>>> driver to create platform-device based on current platform and the last
>>> two converts exynos platform to use this common infrastructure.
>>>
>>> I will migrate rest of the platforms after this is accepted as the right
>>> way ahead.
>>
>> @Matthew and @Mason,
>>
>> Now that this is present in linux-next, you guys can send patches for
>> your platforms cpufreq support.
>
> Present in linux-next means it will show up in 4.6-rc5?

No, it doesn't, in general.

Bug fixes may show up in -rcX, X > 1, but the majority of new material
in linux-next will show up in the next -rc1 (4.7-rc1 in this
particular case).

  reply	other threads:[~2016-04-20 22:31 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-30  8:15 [PATCH V3 0/4] cpufreq: dt: Create platform device from generic code Viresh Kumar
2016-03-30  8:15 ` [PATCH V3 1/4] cpufreq: dt: Include types.h from cpufreq-dt.h Viresh Kumar
2016-03-30  8:15 ` [PATCH V3 2/4] cpufreq: dt: Add generic platform-device creation support Viresh Kumar
2016-04-13 19:46   ` Matthew McClintock
2016-03-30  8:15 ` [PATCH V3 3/4] ARM: exynos: exynos-cpufreq platform device isn't supported anymore Viresh Kumar
2016-03-30  8:15   ` Viresh Kumar
2016-03-30  8:30   ` Krzysztof Kozlowski
2016-03-30  8:30     ` Krzysztof Kozlowski
2016-03-30  8:30     ` Krzysztof Kozlowski
2016-03-30  8:15 ` [PATCH V3 4/4] cpufreq: exynos: Use generic platdev driver Viresh Kumar
2016-03-30  8:15   ` Viresh Kumar
2016-03-30  8:15   ` Viresh Kumar
2016-04-07  8:31 ` [PATCH V3 0/4] cpufreq: dt: Create platform device from generic code Viresh Kumar
2016-04-20  9:55 ` Viresh Kumar
2016-04-20 21:27   ` Mason
2016-04-20 22:31     ` Rafael J. Wysocki [this message]
2016-04-27 16:47   ` Mason
2016-04-27 16:57     ` Matthew McClintock
2016-04-28  2:27       ` Viresh Kumar

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='CAJZ5v0h0T=XyC2bd3RByAC7mSYqRRcTe9XDVULHRz0Owr3a9Kg@mail.gmail.com' \
    --to=rafael@kernel.org \
    --cc=arnd.bergmann@linaro.org \
    --cc=heiko@sntech.de \
    --cc=k.kozlowski@samsung.com \
    --cc=kgene.kim@samsung.com \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mmcclint@codeaurora.org \
    --cc=rjw@rjwysocki.net \
    --cc=slash.tmp@free.fr \
    --cc=viresh.kumar@linaro.org \
    --cc=xf@rock-chips.com \
    /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.