From: Markus Elfring <Markus.Elfring@web.de>
To: huhai@kylinos.cn, linux-unionfs@vger.kernel.org
Cc: hhtracer@gmail.com, LKML <linux-kernel@vger.kernel.org>,
Amir Goldstein <amir73il@gmail.com>,
Miklos Szeredi <miklos@szeredi.hu>
Subject: Re: [PATCH] ovl: only assign err on error path
Date: Wed, 20 Aug 2025 11:43:14 +0200 [thread overview]
Message-ID: <35d4fc68-fe57-464e-a651-eede49fbf00f@web.de> (raw)
In-Reply-To: <20250820092848.534-1-huhai@kylinos.cn>
…
> Signed-off-by: huhai <huhai@kylinos.cn>
> ---
> fs/overlayfs/super.c | 2 +-
…
Should the personal name be usually different from an email identifier
according to requirements of the Developer's Certificate of Origin?
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.17-rc2#n436
Regards,
Markus
prev parent reply other threads:[~2025-08-20 9:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-20 9:28 huhai
2025-08-20 9:33 ` Amir Goldstein
2025-08-20 9:43 ` 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=35d4fc68-fe57-464e-a651-eede49fbf00f@web.de \
--to=markus.elfring@web.de \
--cc=amir73il@gmail.com \
--cc=hhtracer@gmail.com \
--cc=huhai@kylinos.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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
all inboxes | Powered by JetHome®