From: david.li@starfivetech.com
To: kbuild-all@lists.01.org
Subject: Re: [atishp04:dma_non_coherent_v1 28/42] drivers/video/fbdev/starfive/starfive_fb.c:655:9: sparse: sparse: incorrect type in argument 1 (different address spaces)
Date: Fri, 25 Jun 2021 06:39:11 +0000 [thread overview]
Message-ID: <20210625063911.2820.18338@ml01.vlan13.01.org> (raw)
In-Reply-To: <202106191611.33u2qZLs-lkp@intel.com>
[-- Attachment #1: Type: text/plain, Size: 198 bytes --]
Please update the code from the following gitup,
Our code on GitHub doesn't have this warning
https://github.com/starfive-tech/freelight-u-sdk
Reported-by: kernel test robot <lkp@intel.com>
prev parent reply other threads:[~2021-06-25 6:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-19 8:10 [atishp04:dma_non_coherent_v1 28/42] drivers/video/fbdev/starfive/starfive_fb.c:655:9: sparse: sparse: incorrect type in argument 1 (different address spaces) kernel test robot
2021-06-25 6:39 ` david.li [this message]
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=20210625063911.2820.18338@ml01.vlan13.01.org \
--to=david.li@starfivetech.com \
--cc=kbuild-all@lists.01.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.