From: Markus Elfring <Markus.Elfring@web.de>
To: Henrique Carvalho <henrique.carvalho@suse.com>,
make24@iscas.ac.cn, linux-cifs@vger.kernel.org,
kernel-janitors@vger.kernel.org, Steve French <sfrench@samba.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Bharath SM <bharathsm@microsoft.com>,
Enzo Matsumiya <ematsumiya@suse.de>,
Paulo Alcantara <pc@manguebit.com>,
Ronnie Sahlberg <ronniesahlberg@gmail.com>,
Shyam Prasad N <sprasad@microsoft.com>,
Steve French <smfrench@gmail.com>, Tom Talpey <tom@talpey.com>
Subject: Re: [PATCH v3] smb: client: Handle kstrdup failures for passwords
Date: Mon, 4 Nov 2024 12:06:26 +0100 [thread overview]
Message-ID: <275d4e36-4628-4cfc-b51d-1bd909a6fadd@web.de> (raw)
In-Reply-To: <20241022182126.3353440-1-henrique.carvalho@suse.com>
…
> Signed-off-by: Haoxiang Li <make24@iscas.ac.cn>
How relevant can such information still be according to requirements
for the Developer's Certificate of Origin after different names
were presented for such an email address?
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.12-rc6#n396
https://lore.kernel.org/linux-kernel/?q=make24%40iscas.ac.cn
Regards,
Markus
prev parent reply other threads:[~2024-11-04 11:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-01 6:48 [PATCH] fs: smb: client: Add missing check for kstrdup() Haoxiang Li
2024-07-01 13:01 ` Markus Elfring
2024-10-22 17:15 ` [PATCH v2] fs_context.c: smb3_reconfigure: Handle kstrdup failures for passwords Henrique Carvalho
2024-10-22 18:21 ` [PATCH v3] smb: client: " Henrique Carvalho
2024-10-22 22:21 ` Steve French
2024-11-04 11:06 ` Markus Elfring [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=275d4e36-4628-4cfc-b51d-1bd909a6fadd@web.de \
--to=markus.elfring@web.de \
--cc=bharathsm@microsoft.com \
--cc=ematsumiya@suse.de \
--cc=henrique.carvalho@suse.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=make24@iscas.ac.cn \
--cc=pc@manguebit.com \
--cc=ronniesahlberg@gmail.com \
--cc=sfrench@samba.org \
--cc=smfrench@gmail.com \
--cc=sprasad@microsoft.com \
--cc=tom@talpey.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