From: Lee Jones <lee.jones@linaro.org>
To: syzbot <syzbot+2fa4c81b0e82fb808f38@syzkaller.appspotmail.com>
Cc: linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
sfr@canb.auug.org.au, syzkaller-bugs@googlegroups.com
Subject: Re: linux-next build error (10)
Date: Fri, 17 Jul 2020 15:03:26 +0100 [thread overview]
Message-ID: <20200717140326.GJ3165313@dell> (raw)
In-Reply-To: <00000000000018715505aaa390ed@google.com>
On Fri, 17 Jul 2020, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: aab7ee9f Add linux-next specific files for 20200717
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=123cefcf100000
> kernel config: https://syzkaller.appspot.com/x/.config?x=66b5d44ee3d87c99
> dashboard link: https://syzkaller.appspot.com/bug?extid=2fa4c81b0e82fb808f38
> compiler: gcc (GCC) 10.1.0-syz 20200507
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+2fa4c81b0e82fb808f38@syzkaller.appspotmail.com
>
> drivers/mfd/mfd-core.c:147:17: error: implicit declaration of function 'of_read_number' [-Werror=implicit-function-declaration]
This is fixed already, but thanks for the heads-up.
> ---
> This report is generated by a bot. It may contain errors.
> See https://goo.gl/tpsmEJ for more information about syzbot.
> syzbot engineers can be reached at syzkaller@googlegroups.com.
>
> syzbot will keep track of this issue. See:
> https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
--
Lee Jones [李琼斯]
Senior Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog
prev parent reply other threads:[~2020-07-17 14:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-17 13:59 linux-next build error (10) syzbot
2020-07-17 14:03 ` Lee Jones [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=20200717140326.GJ3165313@dell \
--to=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=syzbot+2fa4c81b0e82fb808f38@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.