mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Yunseong Kim <ysk@kzalloc.com>
Cc: Tejun Heo <tj@kernel.org>, Minchan Kim <minchan@kernel.org>,
	Namhyung Kim <namhyung@kernel.org>,
	Joonsoo Kim <iamjoonsoo.kim@lge.com>,
	Hyunchul Lee <cheol.lee@lge.com>,
	Namjae Jeon <linkinjeon@kernel.org>,
	Chanwoo Choi <cw00.choi@samsung.com>,
	Jaegeuk Kim <jaegeuk@kernel.org>, SeongJae Park <sj@kernel.org>,
	Minwoo Im <minwoo.im@samsung.com>,
	Seung-Woo Kim <sw0312.kim@samsung.com>,
	Kukjin Kim <kgene@kernel.org>, Chanho Min <chanho.min@lge.com>,
	Taehee Yoo <ap420073@gmail.com>, Harry Yoo <harry.yoo@oracle.com>,
	gwan-gyeong.mun@intel.com, yeoreum.yun@arm.com,
	Mingi Cho <mgcho.minic@gmail.com>,
	Hyunwoo Kim <imv4bel@gmail.com>,
	austindh.kim@gmail.com, pmnxis@gmail.com,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Yunseong Kim <ysk@kzalloc.com>
Subject: Re: [PATCH v7] Documentation: cve Korean translation
Date: Fri, 29 Aug 2025 16:05:35 -0600	[thread overview]
Message-ID: <878qj14wcw.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20250823193516.19485-2-ysk@kzalloc.com>

Yunseong Kim <ysk@kzalloc.com> writes:

> Understanding the Linux kernel's CVE handling process is becoming
> increasingly critical. This is especially important for Korean companies
> exporting products to regions like Europe, as they must comply with
> regulations such as the Cyber Resilience Act (CRA).
>
> This translation aims to raise awareness among Korean kernel developers and
> companies, helping them better understand and adhere to the kernel
> community's security practices.
>
> The translation is based on the contributor's direct experience with the
> Linux kernel security bug process and obtaining CVEs. Furthermore,
> completion of the security training program provided by the Linux
> Foundation ensures the necessary accuracy for this documentation.
>
> I have refined the context that was present in v6. The review comments from
> Seongjae have been incorporated.
>
> Signed-off-by: Yunseong Kim <ysk@kzalloc.com>
> Reviewed-by: SeongJae Park <sj@kernel.org>
> ---
>  Documentation/translations/ko_KR/index.rst    |   1 +
>  .../translations/ko_KR/process/cve.rst        | 125 ++++++++++++++++++
>  2 files changed, 126 insertions(+)
>  create mode 100644 Documentation/translations/ko_KR/process/cve.rst

Applied, thanks.

jon

  parent reply	other threads:[~2025-08-29 22:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-23 19:35 Yunseong Kim
2025-08-23 19:56 ` Yunseong Kim
2025-08-29 22:05 ` Jonathan Corbet [this message]
2025-08-29 22:10   ` Jonathan Corbet

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=878qj14wcw.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=ap420073@gmail.com \
    --cc=austindh.kim@gmail.com \
    --cc=chanho.min@lge.com \
    --cc=cheol.lee@lge.com \
    --cc=cw00.choi@samsung.com \
    --cc=gwan-gyeong.mun@intel.com \
    --cc=harry.yoo@oracle.com \
    --cc=iamjoonsoo.kim@lge.com \
    --cc=imv4bel@gmail.com \
    --cc=jaegeuk@kernel.org \
    --cc=kgene@kernel.org \
    --cc=linkinjeon@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgcho.minic@gmail.com \
    --cc=minchan@kernel.org \
    --cc=minwoo.im@samsung.com \
    --cc=namhyung@kernel.org \
    --cc=pmnxis@gmail.com \
    --cc=sj@kernel.org \
    --cc=sw0312.kim@samsung.com \
    --cc=tj@kernel.org \
    --cc=yeoreum.yun@arm.com \
    --cc=ysk@kzalloc.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®