From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Max Filippov <jcmvbkbc@gmail.com>
Cc: kbuild test robot <lkp@intel.com>,
Matt Sickler <Matt.Sickler@daktronics.com>,
kbuild-all@01.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: arch/xtensa/include/asm/uaccess.h:40:22: error: implicit declaration of function 'uaccess_kernel'; did you mean 'getname_kernel'?
Date: Mon, 20 May 2019 11:31:26 +0200 [thread overview]
Message-ID: <20190520093126.GA15326@kroah.com> (raw)
In-Reply-To: <CAMo8BfJnr8j+uqOAMb5FE4ParRYCURqfTdb_1kh0iaqboxpMdg@mail.gmail.com>
On Sun, May 19, 2019 at 10:50:44PM -0700, Max Filippov wrote:
> Hello,
>
> On Sun, May 19, 2019 at 10:39 PM kbuild test robot <lkp@intel.com> wrote:
> > Hi Matt,
> >
> > FYI, the error/warning still remains.
> >
> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> > head: a188339ca5a396acc588e5851ed7e19f66b0ebd9
> > commit: 7df95299b94a63ec67a6389fc02dc25019a80ee8 staging: kpc2000: Add DMA driver
> > date: 4 weeks ago
> > config: xtensa-allmodconfig (attached as .config)
> > compiler: xtensa-linux-gcc (GCC) 8.1.0
> > reproduce:
> > wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> > chmod +x ~/bin/make.cross
> > git checkout 7df95299b94a63ec67a6389fc02dc25019a80ee8
> > # save the attached .config to linux build tree
> > GCC_VERSION=8.1.0 make.cross ARCH=xtensa
> >
> > If you fix the issue, kindly add following tag
> > Reported-by: kbuild test robot <lkp@intel.com>
> >
> > All errors (new ones prefixed by >>):
> >
> > In file included from drivers/staging/kpc2000/kpc_dma/fileops.c:11:
> > arch/xtensa/include/asm/uaccess.h: In function 'clear_user':
> > >> arch/xtensa/include/asm/uaccess.h:40:22: error: implicit declaration of function 'uaccess_kernel'; did you mean 'getname_kernel'? [-Werror=implicit-function-declaration]
> > #define __kernel_ok (uaccess_kernel())
> > ^~~~~~~~~~~~~~
>
> I've posted a fix for this issue here:
> https://lkml.org/lkml/2019/5/8/956
>
> If there are post merge window pull requests planned for the
> staging tree please consider including this fix. Alternatively
> if I could get an ack for this fix I'd submit it in a pull request
> from the xtensa tree.
It's now queued up, sorry, I had to wait for 5.2-rc1 to be released.
thanks,
greg k-h
prev parent reply other threads:[~2019-05-20 9:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-20 4:12 kbuild test robot
2019-05-20 5:50 ` Max Filippov
2019-05-20 9:31 ` Greg Kroah-Hartman [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=20190520093126.GA15326@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Matt.Sickler@daktronics.com \
--cc=jcmvbkbc@gmail.com \
--cc=kbuild-all@01.org \
--cc=linux-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
Powered by JetHome