From: kernel test robot <lkp@intel.com>
To: LiuQingtao <qtliu@mail.ustc.edu.cn>, gregkh@linuxfoundation.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
jirislaby@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, neil.armstrong@linaro.org,
bjorn.andersson@oss.qualcomm.com, marex@nabladev.com,
dev@kael-k.io, mani@kernel.org,
prabhakar.mahadev-lad.rj@bp.renesas.com,
linux-serial@vger.kernel.org, linux-riscv@lists.infradead.org,
liu.wenhong35@zte.com.cn, liu.qingtao2@zte.com.cn,
hu.yuye@zte.com.cn, dai.hualiang@zte.com.cn,
deng.weixian@zte.com.cn, jia.yunxiang@zte.com.cn,
bai.lu5@zte.com.cn, yang.susheng@zte.com.cn,
shen.lin1@zte.com.cn, tan.hu@zte.com.cn, zuo.jiang@zte.com.cn
Subject: Re: [PATCH v1 2/2] LRW UART: serial: add driver for the LRW UART
Date: Sat, 14 Feb 2026 01:50:20 +0800 [thread overview]
Message-ID: <202602140108.kLMOYbwS-lkp@intel.com> (raw)
In-Reply-To: <20260213093334.9217-3-qtliu@mail.ustc.edu.cn>
Hi LiuQingtao,
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 robh/for-next usb/usb-testing usb/usb-next usb/usb-linus linus/master v6.19 next-20260212]
[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/LiuQingtao/LRW-UART-dt-bindings-Add-binding-for-LRW-UART/20260213-173610
base: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git tty-testing
patch link: https://lore.kernel.org/r/20260213093334.9217-3-qtliu%40mail.ustc.edu.cn
patch subject: [PATCH v1 2/2] LRW UART: serial: add driver for the LRW UART
config: riscv-allyesconfig (https://download.01.org/0day-ci/archive/20260214/202602140108.kLMOYbwS-lkp@intel.com/config)
compiler: clang version 16.0.6 (https://github.com/llvm/llvm-project 7cbf1a2591520c2491aa35339f227775f4d3adf6)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260214/202602140108.kLMOYbwS-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/202602140108.kLMOYbwS-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/tty/serial/lrw_uart.c:2266:3: warning: variable 'new_mcfg' is uninitialized when used here [-Wuninitialized]
new_mcfg |= UARTMCFG_UARTEN | UARTMCFG_TXE;
^~~~~~~~
drivers/tty/serial/lrw_uart.c:2246:37: note: initialize the variable 'new_mcfg' to silence this warning
unsigned int old_mcfg = 0, new_mcfg;
^
= 0
1 warning generated.
vim +/new_mcfg +2266 drivers/tty/serial/lrw_uart.c
2240
2241 static void
2242 lrw_uart_console_write(struct console *co, const char *s, unsigned int count)
2243 {
2244 struct lrw_uart_port *sup = lrw_uart_console_ports[co->index];
2245 unsigned int old_fccr = 0, new_fccr;
2246 unsigned int old_mcfg = 0, new_mcfg;
2247 unsigned long flags;
2248 int locked = 1;
2249
2250 clk_enable(sup->clk);
2251
2252 if (oops_in_progress)
2253 locked = uart_port_trylock_irqsave(&sup->port, &flags);
2254 else
2255 uart_port_lock_irqsave(&sup->port, &flags);
2256
2257 /*
2258 * First save the FCCR then disable the interrupts
2259 */
2260 if (!sup->vendor->always_enabled) {
2261 old_fccr = lrw_uart_read(sup, REG_FCCR);
2262 new_fccr = old_fccr & ~UARTFCCR_CTSEN;
2263 lrw_uart_write(new_fccr, sup, REG_FCCR);
2264
2265 old_mcfg = lrw_uart_read(sup, REG_MCFG);
> 2266 new_mcfg |= UARTMCFG_UARTEN | UARTMCFG_TXE;
2267 lrw_uart_write(new_mcfg, sup, REG_MCFG);
2268 }
2269
2270 uart_console_write(&sup->port, s, count, lrw_uart_console_putchar);
2271
2272 /*
2273 * Finally, wait for transmitter to become empty and restore the
2274 * TCR. Allow feature register bits to be inverted to work around
2275 * errata.
2276 */
2277 while ((lrw_uart_read(sup, REG_FR) ^ sup->vendor->inv_fr)
2278 & sup->vendor->fr_busy)
2279 cpu_relax();
2280 if (!sup->vendor->always_enabled) {
2281 lrw_uart_write(old_fccr, sup, REG_FCCR);
2282 lrw_uart_write(old_mcfg, sup, REG_MCFG);
2283 }
2284
2285 if (locked)
2286 uart_port_unlock_irqrestore(&sup->port, flags);
2287
2288 clk_disable(sup->clk);
2289 }
2290
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-02-13 17:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-13 9:33 [PATCH v1 0/2] LRW UART: Patch series for LRW UART driver LiuQingtao
2026-02-13 9:33 ` [PATCH v1 1/2] LRW UART: dt-bindings: Add binding for LRW UART LiuQingtao
2026-02-13 10:00 ` Krzysztof Kozlowski
2026-02-13 14:24 ` Krzysztof Kozlowski
2026-02-13 9:33 ` [PATCH v1 2/2] LRW UART: serial: add driver for the " LiuQingtao
2026-02-13 10:02 ` Krzysztof Kozlowski
2026-02-13 16:27 ` kernel test robot
2026-02-13 17:50 ` kernel test robot [this message]
2026-03-12 13:45 ` Greg KH
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=202602140108.kLMOYbwS-lkp@intel.com \
--to=lkp@intel.com \
--cc=bai.lu5@zte.com.cn \
--cc=bjorn.andersson@oss.qualcomm.com \
--cc=conor+dt@kernel.org \
--cc=dai.hualiang@zte.com.cn \
--cc=deng.weixian@zte.com.cn \
--cc=dev@kael-k.io \
--cc=gregkh@linuxfoundation.org \
--cc=hu.yuye@zte.com.cn \
--cc=jia.yunxiang@zte.com.cn \
--cc=jirislaby@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-serial@vger.kernel.org \
--cc=liu.qingtao2@zte.com.cn \
--cc=liu.wenhong35@zte.com.cn \
--cc=llvm@lists.linux.dev \
--cc=mani@kernel.org \
--cc=marex@nabladev.com \
--cc=neil.armstrong@linaro.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=qtliu@mail.ustc.edu.cn \
--cc=robh@kernel.org \
--cc=shen.lin1@zte.com.cn \
--cc=tan.hu@zte.com.cn \
--cc=yang.susheng@zte.com.cn \
--cc=zuo.jiang@zte.com.cn \
/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