linux-kernel - Re: [PATCH] Documentation/livepatch: Update terminology in livepatch

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date: Wed, 10 Jan 2024 23:50:24 +0530
From: Attreyee M <tintinm2017@...il.com>
To: Jonathan Corbet <corbet@....net>
Cc: Bagas Sanjaya <bagasdotme@...il.com>, jpoimboe@...nel.org, jikos@...nel.org, 
	mbenes@...e.cz, pmladek@...e.com, joe.lawrence@...hat.com, 
	linux-kernel@...r.kernel.org, linux-doc@...r.kernel.org, 
	live-patching@...r.kernel.org
Subject: Re: [PATCH] Documentation/livepatch: Update terminology in livepatch

As Bagas Sanjaya wrote in the email before about the change, I thought
the reason was explained.
I am sorry that I didn't respond to it thinking that.

Thank you
Attreyee Mukherjee

On Wed, 10 Jan 2024 at 23:45, Jonathan Corbet <corbet@....net> wrote:
>
> Attreyee M <tintinm2017@...il.com> writes:
>
> > Hello maintainers,
> >
> > I wanted to ask if this patch of mine is accepted as of now.
>
> You never responded to the question that is still quoted in your
> (unfortunately top-posted) email:
>
> > So this is a classic example of saying what you have done, but not why.
> > What makes this a change that we want?
>
> So no, not accepted.  Even with a proper changelog, though, I'm not sure
> I see the value in that particular change.
>
> jon