From: Charles Yeh <charlesyeh522@gmail.com>
To: gregkh@linuxfoundation.org, johan@kernel.org, linux-usb@vger.kernel.org
Cc: charles-yeh@prolific.com.tw,
Charles Yeh <charlesyeh522@gmail.com>,
kernel test robot <lkp@intel.com>
Subject: [PATCH 2/2] USB: serial: pl2303: add new PID to support PL256X (TYPE_MP)
Date: Wed, 25 Mar 2026 20:01:23 +0800 [thread overview]
Message-ID: <20260325120123.1989-1-charlesyeh522@gmail.com> (raw)
Add support for the PL256X (TYPE_MP) device by adding its PID.
Also fix an unused variable warning in pl2303_update_reg() reported
by the kernel test robot.
Reported-by: kernel test robot <lkp@intel.com>
Closes: https://lore.kernel.org/oe-kbuild-all/202603250523.9ktgw2Ju-lkp@intel.com/
Signed-off-by: Charles Yeh <charlesyeh522@gmail.com>
---
v2:
- Remove unused 'struct device *dev' variable in pl2303_update_reg()
to fix build warning.
---
drivers/usb/serial/pl2303.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/usb/serial/pl2303.c b/drivers/usb/serial/pl2303.c
index e5bbda1d63b3..67b78d2fcc92 100644
--- a/drivers/usb/serial/pl2303.c
+++ b/drivers/usb/serial/pl2303.c
@@ -347,7 +347,6 @@ static int pl2303_vendor_write(struct usb_serial *serial, u16 value, u16 index)
static int pl2303_update_reg(struct usb_serial *serial, u8 reg, u8 mask, u8 val)
{
struct pl2303_serial_private *spriv = usb_get_serial_data(serial);
- struct device *dev = &serial->interface->dev;
int ret = 0;
u8 *buf;
--
2.51.0
next reply other threads:[~2026-03-25 12:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-25 12:01 Charles Yeh [this message]
2026-03-25 13:37 ` [PATCH 2/2] USB: serial: pl2303: add new PID to support PL256X (TYPE_MP) Greg KH
2026-03-27 2:29 ` Charles Yeh
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=20260325120123.1989-1-charlesyeh522@gmail.com \
--to=charlesyeh522@gmail.com \
--cc=charles-yeh@prolific.com.tw \
--cc=gregkh@linuxfoundation.org \
--cc=johan@kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=lkp@intel.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