linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chanwoo Choi <cw00.choi@samsung.com>
To: kbuild test robot <lkp@intel.com>, Lin Huang <hl@rock-chips.com>
Cc: kbuild-all@01.org, heiko@sntech.de, myungjoo.ham@samsung.com,
	mark.yao@rock-chips.com, airlied@linux.ie,
	mturquette@baylibre.com, dbasehore@chromium.org,
	sboyd@codeaurora.org, linux-kernel@vger.kernel.org,
	dri-devel@lists.freedesktop.org, dianders@chromium.org,
	linux-rockchip@lists.infradead.org, kyungmin.park@samsung.com,
	linux-arm-kernel@lists.infradead.org, tixy@linaro.org,
	typ@rock-chips.com, sudeep.holla@arm.com, mark.rutland@arm.com,
	linux-pm@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 4/5] PM / devfreq: rockchip: add devfreq driver for rk3399 dmc
Date: Mon, 05 Sep 2016 09:49:19 +0900	[thread overview]
Message-ID: <57CCC10F.30704@samsung.com> (raw)
In-Reply-To: <201609020953.NltUDqVg%fengguang.wu@intel.com>

Dear all,

This patch rely on both rockchip.git and devfreq.git.
Already, Rockchip SoC Maintainer (Heiko Stuebner) created
the immutable branch[1]. When applying these patches
on devfreq.git with pulling the immutable branch[1],
It looks like that should not be a problem.

[1] http://www.spinics.net/lists/arm-kernel/msg528298.html

Best Regards,
Chanwoo Choi

On 2016년 09월 02일 10:23, kbuild test robot wrote:
> Hi Lin,
> 
> [auto build test ERROR on next-20160825]
> [also build test ERROR on v4.8-rc4]
> [cannot apply to rockchip/for-next devfreq/for-rafael linus/master v4.8-rc4 v4.8-rc3 v4.8-rc2]
> [if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
> [Suggest to use git(>=2.9.0) format-patch --base=<commit> (or --base=auto for convenience) to record what (public, well-known) commit your patch series was built on]
> [Check https://git-scm.com/docs/git-format-patch for more information]
> 
> url:    https://github.com/0day-ci/linux/commits/Lin-Huang/rk3399-support-ddr-frequency-scaling/20160902-063701
> config: arm-allmodconfig (attached as .config)
> compiler: arm-linux-gnueabi-gcc (Debian 5.4.0-6) 5.4.0 20160609
> reproduce:
>         wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
>         chmod +x ~/bin/make.cross
>         # save the attached .config to linux build tree
>         make.cross ARCH=arm 
> 
> All errors (new ones prefixed by >>):
> 
>>> drivers/devfreq/rk3399_dmc.c:29:39: fatal error: soc/rockchip/rockchip_sip.h: No such file or directory
>    compilation terminated.
> 
> vim +29 drivers/devfreq/rk3399_dmc.c
> 
>     23	#include <linux/platform_device.h>
>     24	#include <linux/pm_opp.h>
>     25	#include <linux/regulator/consumer.h>
>     26	#include <linux/rwsem.h>
>     27	#include <linux/suspend.h>
>     28	
>   > 29	#include <soc/rockchip/rockchip_sip.h>
>     30	
>     31	struct dram_timing {
>     32		unsigned int ddr3_speed_bin;
> 
> ---
> 0-DAY kernel test infrastructure                Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all                   Intel Corporation
> 

  reply	other threads:[~2016-09-05  0:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-01 22:31 [PATCH 0/5] rk3399 support ddr frequency scaling Lin Huang
2016-09-01 22:31 ` [PATCH 1/5] Documentation: bindings: add dt documentation for dfi controller Lin Huang
2016-09-02  8:50   ` Chanwoo Choi
2016-09-01 22:31 ` [PATCH 2/5] PM / devfreq: event: support rockchip " Lin Huang
2016-09-01 22:31 ` [PATCH 3/5] Documentation: bindings: add dt documentation for rk3399 dmc Lin Huang
2016-09-02  8:53   ` Chanwoo Choi
2016-09-01 22:31 ` [PATCH 4/5] PM / devfreq: rockchip: add devfreq driver " Lin Huang
2016-09-01 23:17   ` Heiko Stübner
2016-09-02  1:46     ` Chanwoo Choi
2016-09-02  1:23   ` kbuild test robot
2016-09-05  0:49     ` Chanwoo Choi [this message]
2016-09-01 22:31 ` [PATCH 5/5] drm/rockchip: Add dmc notifier in vop driver Lin Huang
2016-09-02  0:34   ` kbuild test robot

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=57CCC10F.30704@samsung.com \
    --to=cw00.choi@samsung.com \
    --cc=airlied@linux.ie \
    --cc=dbasehore@chromium.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dianders@chromium.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=heiko@sntech.de \
    --cc=hl@rock-chips.com \
    --cc=kbuild-all@01.org \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=lkp@intel.com \
    --cc=mark.rutland@arm.com \
    --cc=mark.yao@rock-chips.com \
    --cc=mturquette@baylibre.com \
    --cc=myungjoo.ham@samsung.com \
    --cc=sboyd@codeaurora.org \
    --cc=sudeep.holla@arm.com \
    --cc=tixy@linaro.org \
    --cc=typ@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 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).