linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Suzuki K. Poulose" <Suzuki.Poulose@arm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>, Paul Walmsley <paul@pwsan.com>
Cc: "linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Thierry Reding <treding@nvidia.com>
Subject: Re: linux-next: Tree for Jun 26
Date: Fri, 26 Jun 2015 11:55:47 +0100	[thread overview]
Message-ID: <558D2FB3.1060209@arm.com> (raw)
In-Reply-To: <20150626190857.09cac9cb@canb.auug.org.au>

On 26/06/15 10:08, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20150625:
>
> Dropped tree: edac-amd (rebased and merged into Linus' tree)
>
> The arc tree gained a conflict against Linus' tree.
>
> The vfs tree gained a conflict against the ceph tree.
>
> The modules tree still had its build failure so I applied another patch.
>
> The edac-amd tree gained a conflict against Linus' tree so I dropped it.
>
> The akpm tree lost its build failure.
>
> Non-merge commits (relative to Linus' tree): 6974
>   6148 files changed, 782981 insertions(+), 153587 deletions(-)


I get build failures on ARM64:

$ git log | head
commit 043831b4a4e9a981c4ec6331b6d64b9f62285d5d
Author: Stephen Rothwell <sfr@canb.auug.org.au>
Date:   Fri Jun 26 18:59:50 2015 +1000


drivers/clk/tegra/clk-dfll.c: In function ‘find_lut_index_for_rate’:
drivers/clk/tegra/clk-dfll.c:691:3: error: implicit declaration of function ‘regulator_list_voltage’ [-Werror=implicit-function-declaration]
    if (regulator_list_voltage(td->vdd_reg, td->i2c_lut[i]) == uv)
    ^
   CC      drivers/clocksource/mmio.o
   CC      fs/proc/softirqs.o
cc1: some warnings being treated as errors
make[3]: *** [drivers/clk/tegra/clk-dfll.o] Error 1
make[2]: *** [drivers/clk/tegra] Error 2
make[1]: *** [drivers/clk] Error 2
make[1]: *** Waiting for unfinished jobs....

This happens due to a missing dependency on CONFIG_REGULATOR by
CONFIG_ARCH_TEGRA

Not sure if the below is a proper fix, but that solves the problem
for me:


diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
index 0f6edb1..7fe2cc0 100644
--- a/arch/arm64/Kconfig
+++ b/arch/arm64/Kconfig
@@ -218,6 +218,7 @@ config ARCH_TEGRA
         select HAVE_CLK
         select PINCTRL
         select RESET_CONTROLLER
+       select REGULATOR
         help
           This enables support for the NVIDIA Tegra SoC family.



Thanks
Suzuki


>
> ----------------------------------------------------------------------------
>
> I have created today's linux-next tree at
> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> (patches at http://www.kernel.org/pub/linux/kernel/next/ ).  If you
> are tracking the linux-next tree using git, you should not use "git pull"
> to do so as that will try to merge the new linux-next release with the
> old one.  You should use "git fetch" and checkout or reset to the new
> master.
>
> You can see which trees have been included by looking in the Next/Trees
> file in the source.  There are also quilt-import.log and merge.log files
> in the Next directory.  Between each merge, the tree was built with
> a ppc64_defconfig for powerpc and an allmodconfig for x86_64 and a
> multi_v7_defconfig for arm. After the final fixups (if any), it is also
> built with powerpc allnoconfig (32 and 64 bit), ppc44x_defconfig and
> allyesconfig (this fails its final link) and i386, sparc, sparc64 and arm
> defconfig.
>
> Below is a summary of the state of the merge.
>
> I am currently merging 221 trees (counting Linus' and 31 trees of patches
> pending for Linus' tree).
>
> Stats about the size of the tree over time can be seen at
> http://neuling.org/linux-next-size.html .
>
> Status of my local build tests will be at
> http://kisskb.ellerman.id.au/linux-next .  If maintainers want to give
> advice about cross compilers/configs that work, we are always open to add
> more builds.
>
> Thanks to Randy Dunlap for doing many randconfig builds.  And to Paul
> Gortmaker for triage and bug fixes.
>

  reply	other threads:[~2015-06-26 10:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-26  9:08 linux-next: Tree for Jun 26 Stephen Rothwell
2015-06-26 10:55 ` Suzuki K. Poulose [this message]
2015-06-26 11:06   ` [PATCH] regulators: Add missing dummy definition for regulator_list_voltage Suzuki K. Poulose
2015-07-07 12:38     ` Mark Brown
2015-07-10 15:14       ` Suzuki K. Poulose
  -- strict thread matches above, loose matches on Subject: below --
2023-06-26  6:37 linux-next: Tree for Jun 26 Stephen Rothwell
2023-06-26  7:16 ` Stephen Rothwell
2020-06-26  7:06 Stephen Rothwell
2019-06-26 13:16 Stephen Rothwell
2018-06-26  4:34 Stephen Rothwell
2017-06-26  6:58 Stephen Rothwell
2014-06-26  6:41 Stephen Rothwell
2013-06-26  8:06 Stephen Rothwell
2012-06-26  6:41 Stephen Rothwell

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=558D2FB3.1060209@arm.com \
    --to=suzuki.poulose@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=paul@pwsan.com \
    --cc=sfr@canb.auug.org.au \
    --cc=treding@nvidia.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).