public inbox for linux-usb@vger.kernel.org
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: Ai Chao <aichao@kylinos.cn>
Cc: gregkh@linuxfoundation.org, b-liu@ti.com, badhri@google.com,
	heikki.krogerus@linux.intel.com, valentina.manea.m@gmail.com,
	shuah@kernel.org, i@zenithal.me, tiwai@suse.de, kees@kernel.org,
	christophe.jaillet@wanadoo.fr, prashanth.k@oss.qualcomm.com,
	khtsai@google.com, dan.carpenter@linaro.org, tglx@kernel.org,
	mingo@kernel.org, linux-usb@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/6] USB: serial: ti_usb_3410_5052: Use safer strscpy() instead of strcpy()
Date: Tue, 17 Mar 2026 15:37:24 +0100	[thread overview]
Message-ID: <ablnJJIlFnlNhofA@hovoldconsulting.com> (raw)
In-Reply-To: <20260310094434.3639602-2-aichao@kylinos.cn>

On Tue, Mar 10, 2026 at 05:44:29PM +0800, Ai Chao wrote:
> Use a safer function strscpy() instead of strcpy() for copying to
> arrays.
> 
> Only idiomatic code replacement, and no functional changes.
> 
> Signed-off-by: Ai Chao <aichao@kylinos.cn>
> ---

I've applied this one (1/6) for 7.1. Thanks.

Johan

  reply	other threads:[~2026-03-17 14:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-10  9:44 [PATCH 0/6] Use safer strscpy() instead of strcpy() Ai Chao
2026-03-10  9:44 ` [PATCH 1/6] USB: serial: ti_usb_3410_5052: " Ai Chao
2026-03-17 14:37   ` Johan Hovold [this message]
2026-03-10  9:44 ` [PATCH 2/6] usb: musb: " Ai Chao
2026-03-10  9:44 ` [PATCH 3/6] usb: gadget: functionfs: " Ai Chao
2026-03-10  9:44 ` [PATCH 4/6] usb: typec: tcpm: " Ai Chao
2026-03-10  9:44 ` [PATCH 5/6] usb: gadget: udc: " Ai Chao
2026-03-10  9:44 ` [PATCH 6/6] usbip: vhci_sysfs: " Ai Chao
2026-03-10 22:10   ` Shuah Khan
2026-03-11  7:22     ` Dan Carpenter
2026-03-24 21:34       ` Shuah Khan
2026-03-25 11:09         ` Dan Carpenter

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=ablnJJIlFnlNhofA@hovoldconsulting.com \
    --to=johan@kernel.org \
    --cc=aichao@kylinos.cn \
    --cc=b-liu@ti.com \
    --cc=badhri@google.com \
    --cc=christophe.jaillet@wanadoo.fr \
    --cc=dan.carpenter@linaro.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=i@zenithal.me \
    --cc=kees@kernel.org \
    --cc=khtsai@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=prashanth.k@oss.qualcomm.com \
    --cc=shuah@kernel.org \
    --cc=tglx@kernel.org \
    --cc=tiwai@suse.de \
    --cc=valentina.manea.m@gmail.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