From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 01/14] vboxsf: move from strlcpy with unused retval to strscpy
Date: Sat, 20 Aug 2022 10:18:07 +0200 [thread overview]
Message-ID: <YwCYv9esPb200L3k@shikoro> (raw)
In-Reply-To: <0d44fb03-0481-2f0d-eeb5-63cbddeffc62@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 227 bytes --]
> Note you send this one twice. Since I'm not sure which one
> will end up getting merged, I'm going to just reply to both...
Ouch, yes, I sent out all subfolders in fs/ twice. Will fix my scripts,
I am sorry for the noise!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2022-08-20 8:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 21:01 [PATCH 01/14] vboxsf: move from strlcpy with unused retval to strscpy Wolfram Sang
2022-08-18 21:01 ` [PATCH 02/14] reiserfs: " Wolfram Sang
2022-08-18 21:01 ` [PATCH 03/14] proc: " Wolfram Sang
2022-08-18 21:01 ` [PATCH 04/14] ocfs2: " Wolfram Sang
2022-08-21 13:24 ` Joseph Qi
2022-08-18 21:01 ` [PATCH 05/14] NFSD: " Wolfram Sang
2022-08-18 21:08 ` Chuck Lever III
2022-08-19 5:41 ` Wolfram Sang
2022-08-18 21:01 ` [PATCH 06/14] NFS: " Wolfram Sang
2022-08-18 21:01 ` [PATCH 07/14] lockd: " Wolfram Sang
2022-08-18 21:01 ` [PATCH 08/14] hostfs: " Wolfram Sang
2022-08-18 21:01 ` [PATCH 09/14] gfs2: " Wolfram Sang
2022-08-18 21:01 ` [PATCH 10/14] dlm: " Wolfram Sang
2022-08-18 21:01 ` [PATCH 11/14] cifs: " Wolfram Sang
2022-08-18 21:01 ` [PATCH 12/14] befs: " Wolfram Sang
2022-08-18 21:01 ` [PATCH 13/14] affs: " Wolfram Sang
2022-08-18 21:01 ` [PATCH 14/14] fs: " Wolfram Sang
2022-08-19 9:01 ` [PATCH 01/14] vboxsf: " Hans de Goede
2022-08-20 8:18 ` Wolfram Sang [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=YwCYv9esPb200L3k@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=hdegoede@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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