From: "Andrew Jeffery" <andrew@aj.id.au>
To: "Neal Liu" <neal_liu@aspeedtech.com>
Cc: "kbuild test robot" <lkp@intel.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
devicetree@vger.kernel.org, linux-aspeed@lists.ozlabs.org,
linux-arm-msm@vger.kernel.org, amd-gfx@lists.freedesktop.org,
"Linux Memory Management List" <linux-mm@kvack.org>,
kvmarm@lists.linux.dev, linux-riscv@lists.infradead.org,
kvmarm@lists.cs.columbia.edu,
linux-arm-kernel@lists.infradead.org,
linux-trace-kernel@vger.kernel.org
Subject: Re: [linux-next:master] BUILD REGRESSION 66eee64b235411d512bed4d672c2d00683239daf
Date: Thu, 02 Feb 2023 11:37:20 +1030 [thread overview]
Message-ID: <76f4dea0-9a39-4238-a213-0167477f5d54@app.fastmail.com> (raw)
In-Reply-To: <63da97b5.3V1HSQEat507LFIr%lkp@intel.com>
Hi Neal,
On Thu, 2 Feb 2023, at 03:17, kernel test robot wrote:
> tree/branch:
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> master
> branch HEAD: 66eee64b235411d512bed4d672c2d00683239daf Add linux-next
> specific files for 20230201
>
>
> Unverified Error/Warning (likely false positive, please contact us if
> interested):
>
> drivers/crypto/aspeed/aspeed-acry.c:295:37: sparse: sparse: incorrect
> type in assignment (different base types)
> drivers/crypto/aspeed/aspeed-acry.c:305:28: sparse: sparse: cast
> removes address space '__iomem' of expression
> drivers/crypto/aspeed/aspeed-acry.c:606:24: sparse: sparse: symbol
> 'aspeed_acry_akcipher_algs' was not declared. Should it be static?
Can you please look into these issues with the ACRY driver?
Cheers,
Andrew
>
> elapsed time: 722m
>
> configs tested: 69
> configs skipped: 2
>
> gcc tested configs:
> x86_64 rhel-8.3-func
> x86_64 rhel-8.3-kselftests
> ia64 allmodconfig
> x86_64 allnoconfig
> um i386_defconfig
> um x86_64_defconfig
> arc defconfig
> i386 defconfig
> x86_64 defconfig
> alpha defconfig
> arm defconfig
> mips allyesconfig
> x86_64 rhel-8.3-syz
> x86_64 randconfig-a001-20230130
> x86_64 rhel-8.3-kunit
> x86_64 randconfig-a003-20230130
> x86_64 rhel-8.3-bpf
> powerpc allnoconfig
> x86_64 randconfig-a004-20230130
> x86_64 rhel-8.3
> x86_64 randconfig-a002-20230130
> powerpc allmodconfig
> sh allmodconfig
> x86_64 randconfig-a006-20230130
> x86_64 allyesconfig
> i386 randconfig-a001
> x86_64 rhel-8.3-kvm
> i386 randconfig-a003
> x86_64 randconfig-a005-20230130
> arm64 allyesconfig
> i386 allyesconfig
> i386 randconfig-a005
> arc randconfig-r043-20230129
> i386 randconfig-c001
> arm allyesconfig
> s390 defconfig
> s390 allmodconfig
> arm randconfig-r046-20230129
> arm randconfig-r046-20230130
> s390 allyesconfig
> arc randconfig-r043-20230130
> m68k allyesconfig
> m68k allmodconfig
> alpha allyesconfig
> arc allyesconfig
>
> clang tested configs:
> x86_64 rhel-8.3-rust
> x86_64 randconfig-a012-20230130
> x86_64 randconfig-a013-20230130
> x86_64 randconfig-a011-20230130
> x86_64 randconfig-a014-20230130
> i386 randconfig-a013-20230130
> i386 randconfig-a002
> i386 randconfig-a012-20230130
> i386 randconfig-a014-20230130
> i386 randconfig-a004
> x86_64 randconfig-a015-20230130
> i386 randconfig-a015-20230130
> x86_64 randconfig-a016-20230130
> i386 randconfig-a011-20230130
> hexagon randconfig-r041-20230129
> i386 randconfig-a016-20230130
> riscv randconfig-r042-20230129
> i386 randconfig-a006
> riscv randconfig-r042-20230130
> hexagon randconfig-r045-20230130
> hexagon randconfig-r041-20230130
> hexagon randconfig-r045-20230129
> s390 randconfig-r044-20230129
> s390 randconfig-r044-20230130
>
> --
> 0-DAY CI Kernel Test Service
> https://github.com/intel/lkp-tests
next prev parent reply other threads:[~2023-02-02 1:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 16:47 [linux-next:master] BUILD REGRESSION 66eee64b235411d512bed4d672c2d00683239daf kernel test robot
2023-02-02 1:07 ` Andrew Jeffery [this message]
2023-02-02 2:59 ` Neal Liu
2023-02-02 5:18 ` Andrew Jeffery
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=76f4dea0-9a39-4238-a213-0167477f5d54@app.fastmail.com \
--to=andrew@aj.id.au \
--cc=akpm@linux-foundation.org \
--cc=amd-gfx@lists.freedesktop.org \
--cc=devicetree@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-mm@kvack.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=neal_liu@aspeedtech.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).