mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Anson Huang <Anson.Huang@nxp.com>
Cc: kbuild-all@01.org, shawnguo@kernel.org, s.hauer@pengutronix.de,
	kernel@pengutronix.de, fabio.estevam@nxp.com, robh+dt@kernel.org,
	mark.rutland@arm.com, mturquette@baylibre.com, sboyd@kernel.org,
	shengjiu.wang@nxp.com, linux-arm-kernel@lists.infradead.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-clk@vger.kernel.org, Linux-imx@nxp.com
Subject: Re: [PATCH 1/2] clk: imx: add ocram_s clock for i.mx6sx
Date: Tue, 10 Jul 2018 20:06:50 +0800	[thread overview]
Message-ID: <201807101933.aFKUdqqV%fengguang.wu@intel.com> (raw)
In-Reply-To: <1531211979-2179-1-git-send-email-Anson.Huang@nxp.com>

[-- Attachment #1: Type: text/plain, Size: 1576 bytes --]

Hi Anson,

Thank you for the patch! Perhaps something to improve:

[auto build test WARNING on shawnguo/for-next]
[also build test WARNING on v4.18-rc4 next-20180709]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]

url:    https://github.com/0day-ci/linux/commits/Anson-Huang/clk-imx-add-ocram_s-clock-for-i-mx6sx/20180710-171526
base:   https://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git for-next
config: arm-omap2plus_defconfig (attached as .config)
compiler: arm-linux-gnueabi-gcc (Debian 7.2.0-11) 7.2.0
reproduce:
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # save the attached .config to linux build tree
        GCC_VERSION=7.2.0 make.cross ARCH=arm 

All warnings (new ones prefixed by >>):

   In file included from arch/arm/boot/dts/imx6sx.dtsi:5:0,
                    from arch/arm/boot/dts/imx6sx-nitrogen6sx.dts:44:
>> scripts/dtc/include-prefixes/dt-bindings/clock/imx6sx-clock.h:282:0: warning: "IMX6SX_CLK_OCRAM_S" redefined
    #define IMX6SX_CLK_OCRAM_S  269
    
   scripts/dtc/include-prefixes/dt-bindings/clock/imx6sx-clock.h:170:0: note: this is the location of the previous definition
    #define IMX6SX_CLK_OCRAM_S  157
    

vim +/IMX6SX_CLK_OCRAM_S +282 scripts/dtc/include-prefixes/dt-bindings/clock/imx6sx-clock.h

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 33963 bytes --]

  parent reply	other threads:[~2018-07-10 12:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-10  8:39 Anson Huang
2018-07-10  8:39 ` [PATCH 2/2] ARM: dts: imx6sx: add ocram_s support Anson Huang
2018-07-10 12:06 ` kbuild test robot [this message]
2018-07-10 12:12 ` [PATCH 1/2] clk: imx: add ocram_s clock for i.mx6sx 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=201807101933.aFKUdqqV%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=Anson.Huang@nxp.com \
    --cc=Linux-imx@nxp.com \
    --cc=devicetree@vger.kernel.org \
    --cc=fabio.estevam@nxp.com \
    --cc=kbuild-all@01.org \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mturquette@baylibre.com \
    --cc=robh+dt@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=sboyd@kernel.org \
    --cc=shawnguo@kernel.org \
    --cc=shengjiu.wang@nxp.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

all inboxes | Powered by JetHome®