From: kernel test robot <lkp@intel.com>
To: Ryo Takakura <ryotkkr98@gmail.com>,
alex@ghiti.fr, aou@eecs.berkeley.edu, bigeasy@linutronix.de,
conor.dooley@microchip.com, gregkh@linuxfoundation.org,
jirislaby@kernel.org, john.ogness@linutronix.de,
palmer@dabbelt.com, paul.walmsley@sifive.com, pmladek@suse.com,
samuel.holland@sifive.com, u.kleine-koenig@baylibre.com
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org, linux-serial@vger.kernel.org,
Ryo Takakura <ryotkkr98@gmail.com>
Subject: Re: [PATCH v2] serial: sifive: Switch to nbcon console
Date: Sun, 6 Apr 2025 08:48:12 +0800 [thread overview]
Message-ID: <202504060816.EWk91sJS-lkp@intel.com> (raw)
In-Reply-To: <20250405145915.493173-1-ryotkkr98@gmail.com>
Hi Ryo,
kernel test robot noticed the following build warnings:
[auto build test WARNING on tty/tty-testing]
[also build test WARNING on tty/tty-next tty/tty-linus linus/master v6.14 next-20250404]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Ryo-Takakura/serial-sifive-Switch-to-nbcon-console/20250405-230051
base: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git tty-testing
patch link: https://lore.kernel.org/r/20250405145915.493173-1-ryotkkr98%40gmail.com
patch subject: [PATCH v2] serial: sifive: Switch to nbcon console
config: arm-randconfig-002-20250406 (https://download.01.org/0day-ci/archive/20250406/202504060816.EWk91sJS-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 7.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250406/202504060816.EWk91sJS-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/202504060816.EWk91sJS-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/tty/serial/sifive.c:155: warning: Function parameter or struct member 'console_line_ended' not described in 'sifive_serial_port'
vim +155 drivers/tty/serial/sifive.c
45c054d0815b15 Paul Walmsley 2019-04-12 131
45c054d0815b15 Paul Walmsley 2019-04-12 132 /*
45c054d0815b15 Paul Walmsley 2019-04-12 133 *
45c054d0815b15 Paul Walmsley 2019-04-12 134 */
45c054d0815b15 Paul Walmsley 2019-04-12 135
45c054d0815b15 Paul Walmsley 2019-04-12 136 /**
180bb243de730c Lee Jones 2020-11-04 137 * struct sifive_serial_port - driver-specific data extension to struct uart_port
45c054d0815b15 Paul Walmsley 2019-04-12 138 * @port: struct uart_port embedded in this struct
45c054d0815b15 Paul Walmsley 2019-04-12 139 * @dev: struct device *
45c054d0815b15 Paul Walmsley 2019-04-12 140 * @ier: shadowed copy of the interrupt enable register
45c054d0815b15 Paul Walmsley 2019-04-12 141 * @baud_rate: UART serial line rate (e.g., 115200 baud)
180bb243de730c Lee Jones 2020-11-04 142 * @clk: reference to this device's clock
45c054d0815b15 Paul Walmsley 2019-04-12 143 * @clk_notifier: clock rate change notifier for upstream clock changes
45c054d0815b15 Paul Walmsley 2019-04-12 144 *
45c054d0815b15 Paul Walmsley 2019-04-12 145 * Configuration data specific to this SiFive UART.
45c054d0815b15 Paul Walmsley 2019-04-12 146 */
45c054d0815b15 Paul Walmsley 2019-04-12 147 struct sifive_serial_port {
45c054d0815b15 Paul Walmsley 2019-04-12 148 struct uart_port port;
45c054d0815b15 Paul Walmsley 2019-04-12 149 struct device *dev;
45c054d0815b15 Paul Walmsley 2019-04-12 150 unsigned char ier;
45c054d0815b15 Paul Walmsley 2019-04-12 151 unsigned long baud_rate;
45c054d0815b15 Paul Walmsley 2019-04-12 152 struct clk *clk;
45c054d0815b15 Paul Walmsley 2019-04-12 153 struct notifier_block clk_notifier;
328ee9dbff3941 Ryo Takakura 2025-04-05 154 bool console_line_ended;
45c054d0815b15 Paul Walmsley 2019-04-12 @155 };
45c054d0815b15 Paul Walmsley 2019-04-12 156
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: Ryo Takakura <ryotkkr98@gmail.com>,
alex@ghiti.fr, aou@eecs.berkeley.edu, bigeasy@linutronix.de,
conor.dooley@microchip.com, gregkh@linuxfoundation.org,
jirislaby@kernel.org, john.ogness@linutronix.de,
palmer@dabbelt.com, paul.walmsley@sifive.com, pmladek@suse.com,
samuel.holland@sifive.com, u.kleine-koenig@baylibre.com
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org, linux-serial@vger.kernel.org,
Ryo Takakura <ryotkkr98@gmail.com>
Subject: Re: [PATCH v2] serial: sifive: Switch to nbcon console
Date: Sun, 6 Apr 2025 08:48:12 +0800 [thread overview]
Message-ID: <202504060816.EWk91sJS-lkp@intel.com> (raw)
In-Reply-To: <20250405145915.493173-1-ryotkkr98@gmail.com>
Hi Ryo,
kernel test robot noticed the following build warnings:
[auto build test WARNING on tty/tty-testing]
[also build test WARNING on tty/tty-next tty/tty-linus linus/master v6.14 next-20250404]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Ryo-Takakura/serial-sifive-Switch-to-nbcon-console/20250405-230051
base: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git tty-testing
patch link: https://lore.kernel.org/r/20250405145915.493173-1-ryotkkr98%40gmail.com
patch subject: [PATCH v2] serial: sifive: Switch to nbcon console
config: arm-randconfig-002-20250406 (https://download.01.org/0day-ci/archive/20250406/202504060816.EWk91sJS-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 7.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250406/202504060816.EWk91sJS-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/202504060816.EWk91sJS-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/tty/serial/sifive.c:155: warning: Function parameter or struct member 'console_line_ended' not described in 'sifive_serial_port'
vim +155 drivers/tty/serial/sifive.c
45c054d0815b15 Paul Walmsley 2019-04-12 131
45c054d0815b15 Paul Walmsley 2019-04-12 132 /*
45c054d0815b15 Paul Walmsley 2019-04-12 133 *
45c054d0815b15 Paul Walmsley 2019-04-12 134 */
45c054d0815b15 Paul Walmsley 2019-04-12 135
45c054d0815b15 Paul Walmsley 2019-04-12 136 /**
180bb243de730c Lee Jones 2020-11-04 137 * struct sifive_serial_port - driver-specific data extension to struct uart_port
45c054d0815b15 Paul Walmsley 2019-04-12 138 * @port: struct uart_port embedded in this struct
45c054d0815b15 Paul Walmsley 2019-04-12 139 * @dev: struct device *
45c054d0815b15 Paul Walmsley 2019-04-12 140 * @ier: shadowed copy of the interrupt enable register
45c054d0815b15 Paul Walmsley 2019-04-12 141 * @baud_rate: UART serial line rate (e.g., 115200 baud)
180bb243de730c Lee Jones 2020-11-04 142 * @clk: reference to this device's clock
45c054d0815b15 Paul Walmsley 2019-04-12 143 * @clk_notifier: clock rate change notifier for upstream clock changes
45c054d0815b15 Paul Walmsley 2019-04-12 144 *
45c054d0815b15 Paul Walmsley 2019-04-12 145 * Configuration data specific to this SiFive UART.
45c054d0815b15 Paul Walmsley 2019-04-12 146 */
45c054d0815b15 Paul Walmsley 2019-04-12 147 struct sifive_serial_port {
45c054d0815b15 Paul Walmsley 2019-04-12 148 struct uart_port port;
45c054d0815b15 Paul Walmsley 2019-04-12 149 struct device *dev;
45c054d0815b15 Paul Walmsley 2019-04-12 150 unsigned char ier;
45c054d0815b15 Paul Walmsley 2019-04-12 151 unsigned long baud_rate;
45c054d0815b15 Paul Walmsley 2019-04-12 152 struct clk *clk;
45c054d0815b15 Paul Walmsley 2019-04-12 153 struct notifier_block clk_notifier;
328ee9dbff3941 Ryo Takakura 2025-04-05 154 bool console_line_ended;
45c054d0815b15 Paul Walmsley 2019-04-12 @155 };
45c054d0815b15 Paul Walmsley 2019-04-12 156
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-04-06 0:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-05 14:59 [PATCH v2] serial: sifive: Switch to nbcon console Ryo Takakura
2025-04-05 14:59 ` Ryo Takakura
2025-04-06 0:48 ` kernel test robot [this message]
2025-04-06 0:48 ` kernel test robot
2025-04-07 12:39 ` Ryo Takakura
2025-04-07 12:39 ` Ryo Takakura
2025-04-10 12:29 ` Petr Mladek
2025-04-10 12:29 ` Petr Mladek
2025-04-10 14:19 ` Ryo Takakura
2025-04-10 14:19 ` Ryo Takakura
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=202504060816.EWk91sJS-lkp@intel.com \
--to=lkp@intel.com \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=bigeasy@linutronix.de \
--cc=conor.dooley@microchip.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-serial@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=pmladek@suse.com \
--cc=ryotkkr98@gmail.com \
--cc=samuel.holland@sifive.com \
--cc=u.kleine-koenig@baylibre.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.