From: Zhangshaokun <zhangshaokun@hisilicon•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Will Deacon <will@kernel•org>
Subject: Re: linux-next: Tree for Jul 2
Date: Tue, 2 Jul 2019 18:40:45 +0800 [thread overview]
Message-ID: <000f56ac-2abc-bc6a-e2db-5ae38779d276@hisilicon.com> (raw)
In-Reply-To: <20190702195158.79aa5517@canb.auug.org.au>
+Cc: Will Deacon
There is a compiler failure on arm64 platform, as follow:
In file included from ./include/linux/list.h:9:0,
from ./include/linux/kobject.h:19,
from ./include/linux/of.h:17,
from ./include/linux/irqdomain.h:35,
from ./include/linux/acpi.h:13,
from drivers/iommu/arm-smmu-v3.c:12:
drivers/iommu/arm-smmu-v3.c: In function ‘arm_smmu_device_hw_probe’:
drivers/iommu/arm-smmu-v3.c:194:40: error: ‘CONFIG_CMA_ALIGNMENT’ undeclared (first use in this function)
#define Q_MAX_SZ_SHIFT (PAGE_SHIFT + CONFIG_CMA_ALIGNMENT)
^
It's the commit <d25f6ead162e> ("iommu/arm-smmu-v3: Increase maximum size of queues")
Thanks,
Shaokun
On 2019/7/2 17:51, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20190701:
>
> New trees: iomap, djw-vfs
>
> The m68knommu tree gained conflicts against the m68k tree.
>
> The xfs tree lost its build failure.
>
> The pm tree lost its build failure.
>
> The rdma tree still had its build failures so I used the version from
> next-20190628.
>
> The net-next tree gained a conflict against the net tree.
>
> The mlx5-next tree gained conflicts against Linus' tree.
>
> The tip tree gained a conflict against the btrfs-kdave tree which
> required a merge fix patch.
>
> The hmm tree gained build failures due to interactions with the tip and
> drm trees for which I added a merge fix patch and disabled a driver.
>
> Non-merge commits (relative to Linus' tree): 10449
> 10116 files changed, 811540 insertions(+), 297040 deletions(-)
>
> ----------------------------------------------------------------------------
>
> 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, an allmodconfig for x86_64, a
> multi_v7_defconfig for arm and a native build of tools/perf. After
> the final fixups (if any), I do an x86_64 modules_install followed by
> builds for x86_64 allnoconfig, powerpc allnoconfig (32 and 64 bit),
> ppc44x_defconfig, allyesconfig and pseries_le_defconfig and i386, sparc
> and sparc64 defconfig. And finally, a simple boot test of the powerpc
> pseries_le_defconfig kernel in qemu (with and without kvm enabled).
>
> Below is a summary of the state of the merge.
>
> I am currently merging 299 trees (counting Linus' and 72 trees of bug
> fix patches pending for the current merge release).
>
> 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.
>
next prev parent reply other threads:[~2019-07-02 10:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-02 9:51 linux-next: Tree for Jul 2 Stephen Rothwell
2019-07-02 10:40 ` Zhangshaokun [this message]
2019-07-02 12:03 ` Will Deacon
2019-07-02 12:22 ` Zhangshaokun
2019-07-02 15:14 ` Joerg Roedel
2019-07-02 18:47 ` linux-next: Tree for Jul 2 (objtool) Randy Dunlap
2019-07-03 16:44 ` Josh Poimboeuf
2019-07-03 17:23 ` Randy Dunlap
2019-07-03 19:45 ` Josh Poimboeuf
2019-07-03 19:46 ` Josh Poimboeuf
2019-07-03 21:03 ` Josh Poimboeuf
-- strict thread matches above, loose matches on Subject: below --
2025-07-02 10:13 linux-next: Tree for Jul 2 Stephen Rothwell
2024-07-02 7:54 Stephen Rothwell
2020-07-02 6:15 Stephen Rothwell
2018-07-02 4:51 Stephen Rothwell
2015-07-02 5:30 Stephen Rothwell
2014-07-02 6:50 Stephen Rothwell
2013-07-02 7:07 Stephen Rothwell
2013-07-02 10:37 ` Sedat Dilek
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=000f56ac-2abc-bc6a-e2db-5ae38779d276@hisilicon.com \
--to=zhangshaokun@hisilicon$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=will@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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