From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Dario Binacchi <dario.binacchi@amarulasolutions.com>,
linux-can <linux-can@vger.kernel.org>
Subject: Re: [linux-next:master] BUILD REGRESSION 4662b7adea50bb62e993a67f611f3be625d3df0d
Date: Sun, 17 Jul 2022 15:58:25 +0200 [thread overview]
Message-ID: <2d6d9627-bc98-07e9-dbcb-5f317913f5aa@hartkopp.net> (raw)
In-Reply-To: <62cf77c3.3T/sxYUjJq0ImGp4%lkp@intel.com>
Hi Dario,
did you see this build regression too?
On 14.07.22 03:56, kernel test robot wrote:
> tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> branch HEAD: 4662b7adea50bb62e993a67f611f3be625d3df0d Add linux-next specific files for 20220713
>
> Error/Warning reports:
(..)
> drivers/net/can/slcan/slcan-core.c:601:14: sparse: void *
> drivers/net/can/slcan/slcan-core.c:601:14: sparse: void [noderef] __rcu *
> drivers/net/can/slcan/slcan-core.c:601:14: sparse: sparse: incompatible types in comparison expression (different address spaces):
Do you take care on this one?
https://lore.kernel.org/linux-can/20220717025703.pcrf6bseaigsq22r@revolver/T/#m54028de8868a0f653294f6a272a9094378a1cdd7
Best regards,
Oliver
next prev parent reply other threads:[~2022-07-17 13:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-14 1:56 [linux-next:master] BUILD REGRESSION 4662b7adea50bb62e993a67f611f3be625d3df0d kernel test robot
2022-07-14 12:35 ` Russell King (Oracle)
2022-07-14 13:45 ` Philip Li
2022-07-17 1:03 ` Andrew Morton
2022-07-17 2:57 ` Liam Howlett
2022-07-18 13:55 ` Liam Howlett
2022-07-17 13:58 ` Oliver Hartkopp [this message]
2022-07-18 6:52 ` Dario Binacchi
2022-07-18 7:05 ` Oliver Hartkopp
2022-07-18 10:05 ` Marc Kleine-Budde
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=2d6d9627-bc98-07e9-dbcb-5f317913f5aa@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=dario.binacchi@amarulasolutions.com \
--cc=linux-can@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox