public inbox for llvm@lists.linux.dev
 help / color / mirror / Atom feed
From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: jack Livingood <jacklivingood@comcast.net>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	yung-chuan.liao@linux.intel.com, tiwai@suse.de,
	kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] sound:firewire:fixed spelling error
Date: Mon, 24 Feb 2025 09:53:58 +0900	[thread overview]
Message-ID: <20250224005358.GA6489@workstation.local> (raw)
In-Reply-To: <20250219172817.50172-1-jacklivingood@comcast.net>

Hi,

On Wed, Feb 19, 2025 at 09:28:17AM -0800, jack Livingood wrote:
> fixed a spelling error.
> 
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202502191455.cX0HILg0-lkp@intel.com/
> Signed-off-by: Jack Livingood <jacklivingood@comcast.net>
> ---
>  sound/firewire/isight.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

The issued patch does not exist in linux-next branch of sound.git[1]. The
report to which you address is for Sound Open Firmware project[2].

I think it better to re-post the revised-version of patch to replace the
usage of 'strcpy()' with 'strscpy()'[3].


[1] I guess that the maintainer realized the build error when applying
the patch after my review.
[2] https://lore.kernel.org/oe-kbuild-all/202502220137.fyFohYSo-lkp@intel.com/
[3] https://lore.kernel.org/linux-sound/20250205192258.358362-1-jacklivingood@comcast.net/

Thanks

Takashi Sakamoto

      reply	other threads:[~2025-02-24  0:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-19 17:28 [PATCH] sound:firewire:fixed spelling error jack Livingood
2025-02-24  0:53 ` Takashi Sakamoto [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=20250224005358.GA6489@workstation.local \
    --to=o-takashi@sakamocchi.jp \
    --cc=jacklivingood@comcast.net \
    --cc=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=tiwai@suse.de \
    --cc=yung-chuan.liao@linux.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