From: Markus Elfring <Markus.Elfring@web.de>
To: Biancaa Ramesh <biancaa2210329@ssn.edu.in>, linux-kbuild@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Kees Cook <kees@kernel.org>,
Masahiro Yamada <masahiroy@kernel.org>,
Miguel Ojeda <ojeda@kernel.org>,
Nathan Chancellor <nathan@kernel.org>,
Petr Vorel <pvorel@suse.cz>, Thomas Meyer <thomas@m3y3r.de>,
Vegard Nossum <vegard.nossum@oracle.com>
Subject: Re: [PATCH] Kconfig:Uses glibc so strscpy has to be manually- added
Date: Tue, 21 Oct 2025 21:28:20 +0200 [thread overview]
Message-ID: <e8115a3f-da40-49af-9d69-191ea0f280fb@web.de> (raw)
In-Reply-To: <20251021171446.46942-1-biancaa2210329@ssn.edu.in>
…
> ---
> scripts/kconfig/confdata.c | 16 +++++++++++++++-
> scripts/kconfig/symbol.c | 16 +++++++++++++++-
> scripts/kconfig/util.c | 17 ++++++++++++++++-
…
You would like to use the function “strscpy” in these source files.
I miss some information so far.
1. Helpful change description
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.18-rc2#n45
2. Nicer summary phrase
3. More appropriate recipient selection
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.18-rc2#n231
…
> --
> ::DISCLAIMER::
…
> The
> contents of this e-mail and any attachment(s) are confidential and
…
Please reconsider such hints once more for communication by the means of public mailing lists.
https://subspace.kernel.org/etiquette.html#do-not-include-confidentiality-disclaimers
Regards,
Markus
next prev parent reply other threads:[~2025-10-21 19:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-21 17:14 Biancaa Ramesh
2025-10-21 19:28 ` Markus Elfring [this message]
2025-10-22 7:31 ` kernel test robot
2025-10-22 7:41 ` kernel test robot
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=e8115a3f-da40-49af-9d69-191ea0f280fb@web.de \
--to=markus.elfring@web.de \
--cc=biancaa2210329@ssn.edu.in \
--cc=kees@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=ojeda@kernel.org \
--cc=pvorel@suse.cz \
--cc=thomas@m3y3r.de \
--cc=vegard.nossum@oracle.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
all inboxes | Powered by JetHome®