From: kbuild test robot <lkp@intel.com>
To: Grigori Goronzy <greg@chown.ath.cx>
Cc: kbuild-all@01.org, Johan Hovold <johan@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
Grigori Goronzy <greg@chown.ath.cx>
Subject: Re: [PATCH v3 08/13] USB: ch341: add support for RTS/CTS flow control
Date: Mon, 11 Apr 2016 09:27:54 +0800 [thread overview]
Message-ID: <201604110941.19AzEgIZ%fengguang.wu@intel.com> (raw)
In-Reply-To: <1460331833-19836-9-git-send-email-greg@chown.ath.cx>
[-- Attachment #1: Type: text/plain, Size: 1654 bytes --]
Hi Grigori,
[auto build test ERROR on v4.5-rc7]
[cannot apply to usb/usb-testing usb-serial/usb-next v4.6-rc2 v4.6-rc1 next-20160408]
[if your patch is applied to the wrong git tree, please drop us a note to help improving the system]
url: https://github.com/0day-ci/linux/commits/Grigori-Goronzy/USB-ch341-fix-error-handling-on-resume/20160411-075235
config: x86_64-allmodconfig (attached as .config)
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
Note: the linux-review/Grigori-Goronzy/USB-ch341-fix-error-handling-on-resume/20160411-075235 HEAD a1faa3e66e1410087d7b4711181282df9b094024 builds fine.
It only hurts bisectibility.
All errors (new ones prefixed by >>):
drivers/usb/serial/ch341.c: In function 'ch341_set_termios':
>> drivers/usb/serial/ch341.c:403:6: error: 'cflag' undeclared (first use in this function)
if (cflag & CRTSCTS) {
^
drivers/usb/serial/ch341.c:403:6: note: each undeclared identifier is reported only once for each function it appears in
vim +/cflag +403 drivers/usb/serial/ch341.c
397 priv->line_control &= ~(CH341_BIT_DTR | CH341_BIT_RTS);
398 spin_unlock_irqrestore(&priv->lock, flags);
399 }
400
401 ch341_set_handshake(port->serial->dev, priv->line_control);
402
> 403 if (cflag & CRTSCTS) {
404 r = ch341_control_out(port->serial->dev, CH341_REQ_WRITE_REG,
405 CH341_REG_RTSCTS | ((uint16_t)CH341_REG_RTSCTS << 8),
406 0x0101);
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 53124 bytes --]
next prev parent reply other threads:[~2016-04-11 1:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-10 23:43 Major improvements to the ch341 driver v3 Grigori Goronzy
2016-04-10 23:43 ` [PATCH v3 01/13] USB: ch341: fix error handling on resume Grigori Goronzy
2016-04-10 23:43 ` [PATCH v3 02/13] USB: ch341: add LCR register definitions Grigori Goronzy
2016-04-10 23:43 ` [PATCH v3 03/13] USB: ch341: add definitions for modem control Grigori Goronzy
2016-04-10 23:43 ` [PATCH v3 04/13] USB: ch341: fix USB buffer allocations Grigori Goronzy
2016-04-10 23:43 ` [PATCH v3 05/13] USB: ch341: reinitialize chip on reconfiguration Grigori Goronzy
2016-04-10 23:43 ` [PATCH v3 06/13] USB: ch341: add support for parity, frame length, stop bits Grigori Goronzy
2016-04-11 17:25 ` Karl Palsson
2016-04-11 18:25 ` Grigori Goronzy
2016-04-10 23:43 ` [PATCH v3 07/13] USB: ch341: add debug output for chip version Grigori Goronzy
2016-04-10 23:43 ` [PATCH v3 08/13] USB: ch341: add support for RTS/CTS flow control Grigori Goronzy
2016-04-11 1:27 ` kbuild test robot [this message]
2016-04-10 23:43 ` [PATCH v3 09/13] USB: ch341: fix coding style Grigori Goronzy
2016-04-10 23:43 ` [PATCH v3 10/13] USB: ch341: clean up messages Grigori Goronzy
2016-04-10 23:43 ` [PATCH v3 11/13] USB: ch341: improve B0 handling Grigori Goronzy
2016-04-10 23:43 ` [PATCH v3 12/13] USB: ch341: get rid of default configuration Grigori Goronzy
2016-04-10 23:43 ` [PATCH v3 13/13] USB: ch341: implement tx_empty callback Grigori Goronzy
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=201604110941.19AzEgIZ%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=greg@chown.ath.cx \
--cc=gregkh@linuxfoundation.org \
--cc=johan@kernel.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@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
all inboxes | Powered by JetHome®