Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: jack Livingood <jacklivingood@comcast.net>
Cc: clemens@ladisch.de, o-takashi@sakamocchi.jp, linux-sound@vger.kernel.org
Subject: Re: [PATCH 1/2] sounds: firewire: isight: changed strcpy to strscpy
Date: Mon, 10 Feb 2025 18:10:41 +0100	[thread overview]
Message-ID: <874j11afou.wl-tiwai@suse.de> (raw)
In-Reply-To: <20250205192258.358362-1-jacklivingood@comcast.net>

On Wed, 05 Feb 2025 20:22:58 +0100,
jack Livingood wrote:
> 
> From: Jack Livingood <jacklivingood@comcast.net>
> 
> changed strcpy to strscpy in order to prevent a possible linear
> overflow.
> 
> Signed-off-by: Jack Livingood <jacklivingood@comcast.net>

Applied now.  Thanks.


Takashi

      parent reply	other threads:[~2025-02-10 17:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-05 19:22 [PATCH 1/2] sounds: firewire: isight: changed strcpy to strscpy jack Livingood
2025-02-06  0:26 ` Takashi Sakamoto
2025-02-10 17:10 ` Takashi Iwai [this message]

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=874j11afou.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=clemens@ladisch.de \
    --cc=jacklivingood@comcast.net \
    --cc=linux-sound@vger.kernel.org \
    --cc=o-takashi@sakamocchi.jp \
    /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