From: kbuild test robot <lkp@intel.com>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: kbuild-all@01.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.com>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org
Subject: Re: [PATCH v11 1/2] serial: exar: split out the exar code from 8250_pci
Date: Mon, 30 Jan 2017 05:47:41 +0800 [thread overview]
Message-ID: <201701300539.CvVaYT9D%fengguang.wu@intel.com> (raw)
In-Reply-To: <1485722649-7780-1-git-send-email-sudipm.mukherjee@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2103 bytes --]
Hi Sudip,
[auto build test WARNING on tty/tty-testing]
[also build test WARNING on v4.10-rc5 next-20170125]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Sudip-Mukherjee/serial-exar-split-out-the-exar-code-from-8250_pci/20170130-045633
base: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git tty-testing
config: x86_64-rhel (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
Note: it may well be a FALSE warning. FWIW you are at least aware of it now.
http://gcc.gnu.org/wiki/Better_Uninitialized_Warnings
All warnings (new ones prefixed by >>):
drivers/tty/serial/8250/8250_exar.c: In function 'exar_pci_probe':
>> drivers/tty/serial/8250/8250_exar.c:207:49: warning: 'board' may be used uninitialized in this function [-Wmaybe-uninitialized]
maxnr = pci_resource_len(pcidev, bar) >> (board->reg_shift + 3);
~~~~~^~~~~~~~~~~
vim +/board +207 drivers/tty/serial/8250/8250_exar.c
191 port->port.private_data = NULL;
192 }
193
194 static int
195 exar_pci_probe(struct pci_dev *pcidev, const struct pci_device_id *ent)
196 {
197 unsigned int nr_ports, i, bar = 0, maxnr;
198 struct exar8250_board *board;
199 struct uart_8250_port uart;
200 struct exar8250 *priv;
201 int rc;
202
203 rc = pcim_enable_device(pcidev);
204 if (rc)
205 return rc;
206
> 207 maxnr = pci_resource_len(pcidev, bar) >> (board->reg_shift + 3);
208
209 nr_ports = board->num_ports ? board->num_ports : pcidev->device & 0x0f;
210
211 priv = devm_kzalloc(&pcidev->dev, sizeof(*priv) +
212 sizeof(unsigned int) * nr_ports,
213 GFP_KERNEL);
214 if (!priv)
215 return -ENOMEM;
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 38290 bytes --]
prev parent reply other threads:[~2017-01-29 21:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-29 20:44 [PATCH v11 1/2] serial: exar: split out the exar code from 8250_pci Sudip Mukherjee
2017-01-29 20:44 ` [PATCH v11 2/2] serial: 8250_pci: remove exar code Sudip Mukherjee
2017-01-29 21:47 ` kbuild test robot [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=201701300539.CvVaYT9D%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).