From: Shaokun Zhang <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>
Subject: Re: linux-next: Tree for Jul 30 [build failure on arm64]
Date: Fri, 31 Jul 2020 10:46:52 +0800 [thread overview]
Message-ID: <72b073ba-ee41-1a1c-ce6c-ffd8b5936b09@hisilicon.com> (raw)
In-Reply-To: <20200730214659.0fbfdfc4@canb.auug.org.au>
Hi,
There's a build failure on arm64:
In file included from ./include/linux/compat.h:17:0,
from ./arch/arm64/include/asm/stat.h:13,
from ./include/linux/stat.h:6,
from ./include/linux/sysfs.h:22,
from ./include/linux/kobject.h:20,
from ./include/linux/of.h:17,
from ./include/linux/irqdomain.h:35,
from ./include/linux/acpi.h:13,
from ./include/acpi/apei.h:9,
from ./include/acpi/ghes.h:5,
from ./include/linux/arm_sdei.h:8,
from arch/arm64/kernel/asm-offsets.c:10:
./include/linux/fs.h: In function ‘vfs_whiteout’:
./include/linux/fs.h:1709:32: error: ‘S_IFCHR’ undeclared (first use in this function)
return vfs_mknod(dir, dentry, S_IFCHR | WHITEOUT_MODE, WHITEOUT_DEV);
^
./include/linux/fs.h:1709:32: note: each undeclared identifier is reported only once for each
function it appears in
./include/linux/fs.h: At top level:
./include/linux/fs.h:1855:46: warning: ‘struct kstat’ declared inside parameter list
int (*getattr) (const struct path *, struct kstat *, u32, unsigned int);
^
./include/linux/fs.h:1855:46: warning: its scope is only this definition or declaration, which is
probably not what you want
./include/linux/fs.h: In function ‘__mandatory_lock’:
./include/linux/fs.h:2325:25: error: ‘S_ISGID’ undeclared (first use in this function)
return (ino->i_mode & (S_ISGID | S_IXGRP)) == S_ISGID;
^
./include/linux/fs.h:2325:35: error: ‘S_IXGRP’ undeclared (first use in this function)
return (ino->i_mode & (S_ISGID | S_IXGRP)) == S_ISGID;
^
./include/linux/fs.h: In function ‘invalidate_remote_inode’:
./include/linux/fs.h:2588:6: error: implicit declaration of function ‘S_ISREG’
[-Werror=implicit-function-declaration]
if (S_ISREG(inode->i_mode) || S_ISDIR(inode->i_mode) ||
^
./include/linux/fs.h:2588:32: error: implicit declaration of function ‘S_ISDIR’
[-Werror=implicit-function-declaration]
if (S_ISREG(inode->i_mode) || S_ISDIR(inode->i_mode) ||
^
./include/linux/fs.h:2589:6: error: implicit declaration of function ‘S_ISLNK’
[-Werror=implicit-function-declaration]
S_ISLNK(inode->i_mode))
^
./include/linux/fs.h: In function ‘execute_ok’:
./include/linux/fs.h:2768:26: error: ‘S_IXUGO’ undeclared (first use in this function)
return (inode->i_mode & S_IXUGO) || S_ISDIR(inode->i_mode);
Thanks,
Shaokun
在 2020/7/30 19:46, Stephen Rothwell 写道:
> Hi all,
>
> Changes since 20200729:
>
> My fixes tree contains:
>
> dbf24e30ce2e ("device_cgroup: Fix RCU list debugging warning")
>
> Linus' tree gained a build failure for which I revertd a commit.
>
> The vfs tree lost its build failure.
>
> The printk tree lost its build failure.
>
> The net-next tree lost its build failure.
>
> The security tree still had its build failure for which I reverted
> 3 commits.
>
> The iommu tree gained a conflict against the dma-mapping tree.
>
> The tip tree still had its build failure for which I reverted a
> commit.
>
> The vhost tree lost its build failure but gained more for which I applied
> a patch.
>
> The hmm tree gained conflicts against the drm and kvm-ppc trees.
>
> Non-merge commits (relative to Linus' tree): 11751
> 12254 files changed, 603002 insertions(+), 226737 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 htmldocs. 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 328 trees (counting Linus' and 85 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:[~2020-07-31 2:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-30 11:46 linux-next: Tree for Jul 30 Stephen Rothwell
2020-07-30 15:07 ` linux-next: Tree for Jul 30 (drivers/crypto/chelsio/) Randy Dunlap
2020-07-31 2:46 ` Shaokun Zhang [this message]
2020-07-31 4:08 ` linux-next: Tree for Jul 30 [build failure on arm64] Stephen Rothwell
2020-07-31 8:30 ` Naresh Kamboju
2020-07-31 8:53 ` Stephen Rothwell
2020-07-31 9:00 ` Christoph Hellwig
2020-07-31 9:42 ` Stephen Rothwell
2020-07-31 8:56 ` Shaokun Zhang
2020-07-31 9:18 ` Christoph Hellwig
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=72b073ba-ee41-1a1c-ce6c-ffd8b5936b09@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 \
/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