All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <error27@gmail.com>
To: Noah Techoueyres <noahtechoueyres@gmail.com>
Cc: johan@kernel.org, elder@kernel.org, gregkh@linuxfoundation.org,
	greybus-dev@lists.linaro.org, linux-staging@lists.linux.dev
Subject: Re: [PATCH] staging: greybus: Replace strncpy with strscpy
Date: Sat, 8 Aug 2026 10:23:37 +0300	[thread overview]
Message-ID: <anbZeXqXbUAuAFUE@stanley.mountain> (raw)
In-Reply-To: <20260803012620.5503-1-noahtechoueyres@gmail.com>

On Sun, Aug 02, 2026 at 09:26:20PM -0400, Noah Techoueyres wrote:
>  Replace deprecated strncpy() with strscpy() to improve string
>   handling safety. strscpy() guarantees null-termination and is
>   the preferred function per the kernel string handling guidelines.

This white space is weird.  You did't try to compile your patch.

regards,
dan carpenter


      reply	other threads:[~2026-08-08  7:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-03  1:26 [PATCH] staging: greybus: Replace strncpy with strscpy Noah Techoueyres
2026-08-08  7:23 ` Dan Carpenter [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=anbZeXqXbUAuAFUE@stanley.mountain \
    --to=error27@gmail.com \
    --cc=elder@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=greybus-dev@lists.linaro.org \
    --cc=johan@kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=noahtechoueyres@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.