[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAK8P3a16QW6et2v4AihnwuKgz7JaTUhR9tELknUechjLemwjGg@mail.gmail.com>
Date: Mon, 3 Jun 2019 14:38:43 +0200
From: Arnd Bergmann <arnd@...db.de>
To: kbuild test robot <lkp@...el.com>
Cc: kbuild-all@...org, Networking <netdev@...r.kernel.org>,
driverdevel <devel@...verdev.osuosl.org>,
gregkh <gregkh@...uxfoundation.org>
Subject: Re: [net-next:master 391/455] drivers/staging/isdn/avm/b1.c:163:49:
sparse: sparse: incorrect type in argument 2 (different address spaces)
On Mon, Jun 3, 2019 at 1:40 PM kbuild test robot <lkp@...el.com> wrote:
>
> Hi Arnd,
>
> First bad commit (maybe != root cause):
Yep:
> >> drivers/staging/isdn/avm/b1.c:163:49: sparse: sparse: incorrect type in argument 2 (different address spaces) @@ expected void const [noderef] <asn:1> *from @@ got const [noderef] <asn:1> *from @@
> >> drivers/staging/isdn/avm/b1.c:163:49: sparse: expected void const [noderef] <asn:1> *from
> >> drivers/staging/isdn/avm/b1.c:163:49: sparse: got unsigned char *[assigned] dp
I only moved the file, so the warnings are now for a different pathname.
I'll leave it for the staging driver crowd to fix them up, or ignore them as the
driver is on its way out of the kernel.
Arnd
Powered by blists - more mailing lists