From: Johan Hovold <johan@kernel.org>
To: kernel test robot <lkp@intel.com>
Cc: oe-kbuild@lists.linux.dev, Dan Carpenter <error27@gmail.com>,
linux-kernel@vger.kernel.org
Subject: The robot is broken (was: Re: [PATCH 1/3] USB: serial: return errors from break handling)
Date: Sun, 4 Jun 2023 14:41:27 +0200 [thread overview]
Message-ID: <ZHyGd5BRjUaOdYyF@hovoldconsulting.com> (raw)
In-Reply-To: <202306031014.qzAY3uQ6-lkp@intel.com>
On Sat, Jun 03, 2023 at 10:40:42AM +0800, kernel test robot wrote:
> BCC: lkp@intel.com
> CC: oe-kbuild-all@lists.linux.dev
> In-Reply-To: <20230602124642.19076-2-johan@kernel.org>
> References: <20230602124642.19076-2-johan@kernel.org>
> TO: Johan Hovold <johan@kernel.org>
> TO: Johan Hovold <johan@kernel.org>
> CC: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>
> CC: linux-usb@vger.kernel.org
> CC: linux-kernel@vger.kernel.org
> CC: Corey Minyard <minyard@acm.org>
>
> Hi Johan,
>
> kernel test robot noticed the following build warnings:
> New smatch warnings:
> drivers/usb/serial/io_edgeport.c:1601 edge_break() error: uninitialized symbol 'status'.
Thanks for the report. Now fixed up in v2:
https://lore.kernel.org/lkml/20230604123505.4661-1-johan@kernel.org
The robot currently appears to be broken though as this report was never
sent to me or the relevant mailing lists (and I just happened to see it
by chance).
Looks like there's a stray newline in the output of your scripts which
causes the mail headers above to be included in the body instead.
Johan
next parent reply other threads:[~2023-06-04 12:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <202306031014.qzAY3uQ6-lkp@intel.com>
2023-06-04 12:41 ` Johan Hovold [this message]
2023-06-05 4:30 ` Philip Li
2023-06-05 6:50 ` Johan Hovold
2023-06-05 7:44 ` Dan Carpenter
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=ZHyGd5BRjUaOdYyF@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=error27@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild@lists.linux.dev \
/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
Powered by JetHome