public inbox for linux-usb@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Charles Yeh <charlesyeh522@gmail.com>,
	gregkh@linuxfoundation.org, johan@kernel.org,
	linux-usb@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, charles-yeh@prolific.com.tw,
	Charles Yeh <charlesyeh522@gmail.com>
Subject: Re: [PATCH] USB: serial: pl2303: add new PID to support PL256X (TYPE_MP)
Date: Wed, 25 Mar 2026 05:51:53 +0800	[thread overview]
Message-ID: <202603250523.9ktgw2Ju-lkp@intel.com> (raw)
In-Reply-To: <20260324124619.843-1-charlesyeh522@gmail.com>

Hi Charles,

kernel test robot noticed the following build warnings:

[auto build test WARNING on johan-usb-serial/usb-next]
[also build test WARNING on johan-usb-serial/usb-linus usb/usb-testing usb/usb-next usb/usb-linus tty/tty-testing tty/tty-next tty/tty-linus linus/master v7.0-rc5 next-20260324]
[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/Charles-Yeh/USB-serial-pl2303-add-new-PID-to-support-PL256X-TYPE_MP/20260324-235444
base:   https://git.kernel.org/pub/scm/linux/kernel/git/johan/usb-serial.git usb-next
patch link:    https://lore.kernel.org/r/20260324124619.843-1-charlesyeh522%40gmail.com
patch subject: [PATCH] USB: serial: pl2303: add new PID to support PL256X (TYPE_MP)
config: i386-randconfig-141-20260325 (https://download.01.org/0day-ci/archive/20260325/202603250523.9ktgw2Ju-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
smatch: v0.5.0-9004-gb810ac53
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260325/202603250523.9ktgw2Ju-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/202603250523.9ktgw2Ju-lkp@intel.com/

All warnings (new ones prefixed by >>):

   drivers/usb/serial/pl2303.c: In function 'pl2303_update_reg':
>> drivers/usb/serial/pl2303.c:350:24: warning: unused variable 'dev' [-Wunused-variable]
     350 |         struct device *dev = &serial->interface->dev;
         |                        ^~~


vim +/dev +350 drivers/usb/serial/pl2303.c

   346	
   347	static int pl2303_update_reg(struct usb_serial *serial, u8 reg, u8 mask, u8 val)
   348	{
   349		struct pl2303_serial_private *spriv = usb_get_serial_data(serial);
 > 350		struct device *dev = &serial->interface->dev;
   351		int ret = 0;
   352		u8 *buf;
   353	
   354		buf = kmalloc(1, GFP_KERNEL);
   355		if (!buf)
   356			return -ENOMEM;
   357	
   358		if (spriv->type == &pl2303_type_data[TYPE_HXN] ||
   359			spriv->type == &pl2303_type_data[TYPE_MP]) {
   360			ret = pl2303_vendor_read(serial, reg, buf);
   361		} else {
   362			ret = pl2303_vendor_read(serial, reg | 0x80, buf);
   363		}
   364	
   365		if (ret)
   366			goto out_free;
   367	
   368		*buf &= ~mask;
   369		*buf |= val & mask;
   370	
   371		ret = pl2303_vendor_write(serial, reg, *buf);
   372	out_free:
   373		kfree(buf);
   374	
   375		return ret;
   376	}
   377	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

  reply	other threads:[~2026-03-24 21:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-24 12:46 [PATCH] USB: serial: pl2303: add new PID to support PL256X (TYPE_MP) Charles Yeh
2026-03-24 21:51 ` kernel test robot [this message]
2026-03-24 22:15 ` kernel test robot
  -- strict thread matches above, loose matches on Subject: below --
2021-06-22 12:09 [PATCH] USB: serial: pl2303: Add " Charles Yeh
2021-07-22  5:16 ` Charles Yeh
2021-07-22  7:40   ` Johan Hovold
     [not found] ` <CAAZvQQ6Kr0vbDAnKYum9EaCVxc9Ps69vBV+sg2mov06tB4KqNg@mail.gmail.com>
2021-07-22  5:50   ` Greg KH
2021-08-04 10:54 ` Johan Hovold
2021-11-01  4:53   ` Charles Yeh
2021-11-05 10:02     ` 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=202603250523.9ktgw2Ju-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=charles-yeh@prolific.com.tw \
    --cc=charlesyeh522@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=johan@kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --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