From: Neal Liu <neal_liu@aspeedtech.com>
To: Andrew Jeffery <andrew@aj.id.au>
Cc: kbuild test robot <lkp@intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-aspeed@lists.ozlabs.org" <linux-aspeed@lists.ozlabs.org>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>,
Linux Memory Management List <linux-mm@kvack.org>,
"kvmarm@lists.linux.dev" <kvmarm@lists.linux.dev>,
"linux-riscv@lists.infradead.org"
<linux-riscv@lists.infradead.org>,
"kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-trace-kernel@vger.kernel.org"
<linux-trace-kernel@vger.kernel.org>
Subject: RE: [linux-next:master] BUILD REGRESSION 66eee64b235411d512bed4d672c2d00683239daf
Date: Thu, 2 Feb 2023 02:59:18 +0000 [thread overview]
Message-ID: <TY2PR06MB321334CFD4ED1BD4AF97965380D69@TY2PR06MB3213.apcprd06.prod.outlook.com> (raw)
In-Reply-To: <76f4dea0-9a39-4238-a213-0167477f5d54@app.fastmail.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
I just send patch to fix the first 2 warnings, and the last one warning is already fixed by another patch.
[PATCH-next] crypto: aspeed: fix type warnings
https://patchwork.ozlabs.org/project/linux-aspeed/patch/20230119014859.1900136-1-yangyingliang@huawei.com/
Thanks
-Neal
next prev parent reply other threads:[~2023-02-02 2:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 16:47 kernel test robot
2023-02-02 1:07 ` Andrew Jeffery
2023-02-02 2:59 ` Neal Liu [this message]
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=TY2PR06MB321334CFD4ED1BD4AF97965380D69@TY2PR06MB3213.apcprd06.prod.outlook.com \
--to=neal_liu@aspeedtech.com \
--cc=akpm@linux-foundation.org \
--cc=amd-gfx@lists.freedesktop.org \
--cc=andrew@aj.id.au \
--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 \
/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