All of lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <k.kozlowski@samsung.com>
To: MyungJoo Ham <myungjoo.ham@samsung.com>,
	Kyungmin Park <kyungmin.park@samsung.com>,
	Chanwoo Choi <cw00.choi@samsung.com>,
	linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Subject: Re: [PATCH] devfreq: Add COMPILE_TEST for build coverage
Date: Wed, 29 Jun 2016 13:17:54 +0200	[thread overview]
Message-ID: <5773AE62.90206@samsung.com> (raw)
In-Reply-To: <1467035939-31799-1-git-send-email-k.kozlowski@samsung.com>

On 06/27/2016 03:58 PM, Krzysztof Kozlowski wrote:
> The SoC-specific devfreq and event drivers can be build tested on all
> architectures.
> 
> Signed-off-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
> 
> ---
> 
> Success of compilation tested on ARM, ARM64, i386, x86_64 and powerpc
> architectures (allyesconfigs).
> ---
>  drivers/devfreq/Kconfig       | 4 ++--
>  drivers/devfreq/event/Kconfig | 4 ++--
>  2 files changed, 4 insertions(+), 4 deletions(-)

Hi all,

The patchset depends "clk: Provide notifier stubs when
!COMMON_CLKclk-notify" [1] which you can get by merging clk-notify
branch of clk tree:

git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git clk-notify

Can you pull while applying?

Best regards,
Krzysztof


[1]
https://git.kernel.org/cgit/linux/kernel/git/clk/linux.git/commit/?h=clk-notify&id=e81b87d22a8fed6bac24197972c9c394a2b92b5d


  parent reply	other threads:[~2016-06-29 11:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-27 13:58 [PATCH] devfreq: Add COMPILE_TEST for build coverage Krzysztof Kozlowski
2016-06-27 18:37 ` kbuild test robot
2016-06-27 18:37   ` kbuild test robot
2016-06-28  7:32   ` Krzysztof Kozlowski
2016-06-29 11:17 ` Krzysztof Kozlowski [this message]
2016-07-12 10:11   ` MyungJoo Ham

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=5773AE62.90206@samsung.com \
    --to=k.kozlowski@samsung.com \
    --cc=b.zolnierkie@samsung.com \
    --cc=cw00.choi@samsung.com \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=myungjoo.ham@samsung.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.