From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: kernel test robot <lkp@intel.com>
Cc: Brenda Streiff <brenda.streiff@ni.com>,
oe-kbuild-all@lists.linux.dev, linux-serial@vger.kernel.org
Subject: Re: [tty:tty-testing 12/24] drivers/tty/serial/8250/8250_ni.c:446:41: warning: 'nic7a69' defined but not used
Date: Tue, 17 Oct 2023 10:15:55 +0200 [thread overview]
Message-ID: <2023101704-pacifism-audience-97c8@gregkh> (raw)
In-Reply-To: <202310170418.GCOnw1n1-lkp@intel.com>
On Tue, Oct 17, 2023 at 04:37:14AM +0800, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git tty-testing
> head: d7b7027a2dcfb08e3e592c81978551f53c3beb4f
> commit: 59dbecf92fa66c454ba8011231212e3ca51aae28 [12/24] serial: 8250: add driver for NI UARTs
> config: m68k-allyesconfig (https://download.01.org/0day-ci/archive/20231017/202310170418.GCOnw1n1-lkp@intel.com/config)
> compiler: m68k-linux-gcc (GCC) 13.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231017/202310170418.GCOnw1n1-lkp@intel.com/reproduce)
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202310170418.GCOnw1n1-lkp@intel.com/
>
> All warnings (new ones prefixed by >>):
>
> >> drivers/tty/serial/8250/8250_ni.c:446:41: warning: 'nic7a69' defined but not used [-Wunused-const-variable=]
> 446 | static const struct ni16550_device_info nic7a69 = {
> | ^~~~~~~
> >> drivers/tty/serial/8250/8250_ni.c:439:41: warning: 'nic792b' defined but not used [-Wunused-const-variable=]
> 439 | static const struct ni16550_device_info nic792b = {
> | ^~~~~~~
> >> drivers/tty/serial/8250/8250_ni.c:433:41: warning: 'nic7772' defined but not used [-Wunused-const-variable=]
> 433 | static const struct ni16550_device_info nic7772 = {
> | ^~~~~~~
> >> drivers/tty/serial/8250/8250_ni.c:428:41: warning: 'nic7750' defined but not used [-Wunused-const-variable=]
> 428 | static const struct ni16550_device_info nic7750 = {
> | ^~~~~~~
>
>
> vim +/nic7a69 +446 drivers/tty/serial/8250/8250_ni.c
>
> 426
> 427 /* NI 16550 RS-485 Interface */
> > 428 static const struct ni16550_device_info nic7750 = {
> 429 .uartclk = 33333333,
> 430 };
> 431
> 432 /* NI CVS-145x RS-485 Interface */
> > 433 static const struct ni16550_device_info nic7772 = {
> 434 .uartclk = 1843200,
> 435 .flags = NI_HAS_PMR,
> 436 };
> 437
> 438 /* NI cRIO-904x RS-485 Interface */
> > 439 static const struct ni16550_device_info nic792b = {
> 440 /* Sets UART clock rate to 22.222 MHz with 1.125 prescale */
> 441 .uartclk = 22222222,
> 442 .prescaler = 0x09,
> 443 };
> 444
> 445 /* NI sbRIO 96x8 RS-232/485 Interfaces */
> > 446 static const struct ni16550_device_info nic7a69 = {
> 447 /* Set UART clock rate to 29.629 MHz with 1.125 prescale */
> 448 .uartclk = 29629629,
> 449 .prescaler = 0x09,
> 450 };
> 451
I'll go drop this patch, and the one before this in the series from you,
from my tree now, please fix it up and resend.
thanks,
greg k-h
prev parent reply other threads:[~2023-10-17 8:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-16 20:37 [tty:tty-testing 12/24] drivers/tty/serial/8250/8250_ni.c:446:41: warning: 'nic7a69' defined but not used kernel test robot
2023-10-17 8:15 ` Greg Kroah-Hartman [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=2023101704-pacifism-audience-97c8@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=brenda.streiff@ni.com \
--cc=linux-serial@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@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