From: Christoph Hellwig <hch@lst.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Christoph Hellwig <hch@lst.de>, kernel test robot <lkp@intel.com>,
kbuild-all@lists.01.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Greg Ungerer <gerg@linux-m68k.org>,
linux-m68k <linux-m68k@lists.linux-m68k.org>
Subject: Re: [char-misc:char-misc-next 28/28] drivers/char/mem.c:737:21: sparse: sparse: incorrect type in argument 1 (different address spaces)
Date: Mon, 7 Sep 2020 09:14:00 +0200 [thread overview]
Message-ID: <20200907071400.GA19764@lst.de> (raw)
In-Reply-To: <CAMuHMdVTysHJoghpLC5KyX=s7SOFNFxsXKX1m69AseM12x3XRQ@mail.gmail.com>
On Mon, Sep 07, 2020 at 09:04:15AM +0200, Geert Uytterhoeven wrote:
> Hi Christoph,
>
> On Mon, Sep 7, 2020 at 8:25 AM Christoph Hellwig <hch@lst.de> wrote:
> > On Sun, Sep 06, 2020 at 05:14:15AM +0800, kernel test robot wrote:
> > > tree: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git char-misc-next
> > > head: 99f667352f6c938440d9043d0f66f859d6f3d50d
> > > commit: 99f667352f6c938440d9043d0f66f859d6f3d50d [28/28] /dev/zero: also implement ->read
> > > config: m68k-randconfig-s031-20200904 (attached as .config)
> > > compiler: m68k-linux-gcc (GCC) 9.3.0
> >
> > Looks like m68 does not have proper __user annotations for clear_user..
>
> M68k has, m68knommu apparently hasn't.
> Same for strncpy_from_user() and strnlen_user().
Sorry, I mean to write m68knommu, that's why I added Greg to the
Cc list.
next prev parent reply other threads:[~2020-09-07 7:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <202009060512.tOc1hWe8%lkp@intel.com>
2020-09-07 6:24 ` [char-misc:char-misc-next 28/28] drivers/char/mem.c:737:21: sparse: sparse: incorrect type in argument 1 (different address spaces) Christoph Hellwig
2020-09-07 7:04 ` Geert Uytterhoeven
2020-09-07 7:14 ` Christoph Hellwig [this message]
2020-09-08 13:06 ` Greg Ungerer
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=20200907071400.GA19764@lst.de \
--to=hch@lst.de \
--cc=geert@linux-m68k.org \
--cc=gerg@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-m68k@lists.linux-m68k.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