linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Petr Mladek <pmladek@suse.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Documentation <linux-doc@vger.kernel.org>,
	Linux Kernel Livepatching <live-patching@vger.kernel.org>,
	Josh Poimboeuf <jpoimboe@kernel.org>,
	Jiri Kosina <jikos@kernel.org>, Miroslav Benes <mbenes@suse.cz>,
	Joe Lawrence <joe.lawrence@redhat.com>,
	Jonathan Corbet <corbet@lwn.net>,
	Marcos Paulo de Souza <mpdesouza@suse.com>
Subject: Re: [PATCH] Documentation: livepatch: Correct release locks antonym
Date: Tue, 10 Sep 2024 13:01:14 +0200	[thread overview]
Message-ID: <ZuAm-pgXO4SySyB5@pathway.suse.cz> (raw)
In-Reply-To: <cd1340e4-f726-4ac4-9caa-8e8a3c369203@gmail.com>

On Tue 2024-09-10 17:27:42, Bagas Sanjaya wrote:
> On 9/4/24 18:48, Petr Mladek wrote:
> > On Tue 2024-09-03 09:47:53, Bagas Sanjaya wrote:
> > > "get" doesn't properly fit as an antonym for "release" in the context
> > > of locking. Correct it with "acquire".
> > > 
> > > Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
> > 
> > Reviewed-by: Petr Mladek <pmladek@suse.com>
> > 
> > The patch is trivial. I have have committed it into livepatching.git,
> > branch for-6.12/trivial.
> > 
> 
> Shouldn't this for 6.11 instead? I'm expecting that though...

I am sorry but the change is not urgent enough to be rushed into 6.11.

Best Regards,
Petr

  reply	other threads:[~2024-09-10 11:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-03  2:47 [PATCH] Documentation: livepatch: Correct release locks antonym Bagas Sanjaya
2024-09-04 11:48 ` Petr Mladek
2024-09-10 10:27   ` Bagas Sanjaya
2024-09-10 11:01     ` Petr Mladek [this message]
2024-09-10 23:53       ` Bagas Sanjaya

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=ZuAm-pgXO4SySyB5@pathway.suse.cz \
    --to=pmladek@suse.com \
    --cc=bagasdotme@gmail.com \
    --cc=corbet@lwn.net \
    --cc=jikos@kernel.org \
    --cc=joe.lawrence@redhat.com \
    --cc=jpoimboe@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=live-patching@vger.kernel.org \
    --cc=mbenes@suse.cz \
    --cc=mpdesouza@suse.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;
as well as URLs for NNTP newsgroup(s).