Hi James,
On Wed, Apr 18, 2018 at 02:59:15PM +0100, James Simmons wrote:
Hello,
FYI this happens in mainline kernel 4.17.0-rc1.
It looks like a new regression.
[7.587002] lnet_selftest_init+0x2c4/0x5d9:
lnet_selftest_init at
drivers/stagi
On Thu, Mar 15, 2018 at 09:04:04AM +0100, Arnd Bergmann wrote:
On Thu, Mar 15, 2018 at 3:51 AM, Deepa Dinamani wrote:
On Wed, Mar 14, 2018 at 1:52 PM, Arnd Bergmann wrote:
On Wed, Mar 14, 2018 at 4:50 AM, Deepa Dinamani wrote:
The file arch/arm64/kernel/process.c needs asm/compat.h also to
automatically
Generated by: scripts/coccinelle/api/platform_no_drv_owner.cocci
CC: Alan Cox
Signed-off-by: Fengguang Wu
May I ask which repository this patch is based on?
The email is replying to this one, which shows Greg's staging tree.
Date: Wed, 1 Mar 2017 18:30:16 +0800
From: kbuild
to reduce false positives
Generated by: scripts/coccinelle/api/memdup_user.cocci
CC: Sudip Mukherjee
Signed-off-by: Fengguang Wu
---
0 files changed
rule starting on line 17: position variables or mixed modifs interfere with
comm_assoc isobool (
(
(
(unknown *to == NULL)
>>> IS
On Tue, Jul 19, 2016 at 07:52:53PM -0700, David Miller wrote:
From: Dexuan Cui
Date: Wed, 20 Jul 2016 01:48:18 +
From: kbuild test robot [mailto:l...@intel.com]
Sent: Wednesday, July 20, 2016 1:10
Hi,
[auto build test WARNING on net-next/master]
url:https://github.com/0day-ci/linux/
Yes, sorry for the noises!
>> net/hv_sock/af_hvsock.o: warning: objtool: hvsock_on_channel_cb()+0x1d:
function has unreachable instruction
These warnings are all false alarms.
Thanks,
-- Dexuan
___
kbuild-all mailing list
kbuild-...@lists.01.org
htt
L|__GFP_COMP|__GFP_NOTRACK)
Reported-by: Philip Li
Signed-off-by: Fengguang Wu
---
fs/char_dev.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/char_dev.c b/fs/char_dev.c
index 687471d..6edd825 100644
--- a/fs/char_dev.c
+++ b/fs/char_dev.c
@@ -92,7 +92,7 @@ __register_chrdev
On Mon, Mar 02, 2015 at 12:41:05PM +0300, Dan Carpenter wrote:
> On Mon, Mar 02, 2015 at 11:49:23AM +0800, kbuild test robot wrote:
> > drivers/hv/vmbus_drv.c:51:5: sparse: symbol 'hyperv_panic_event' was not
> > declared. Should it be static?
> > drivers/hv/vmbus_drv.c:51:5: sparse: symbol 'hyper
Hi Benjamin,
> Fengguang,
>
> I ran your script against freshly-checked-out source from staging-next, and
> was not able to reproduce the error with it. My boot log is attached. I
> noticed that your log did not have "Hypervisor detected: KVM" in the trace.
> The KVM options in your script als
