From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Leonardo Bras <leobras@redhat.com>
Cc: Jakub Kicinski <kuba@kernel.org>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
Alexei Starovoitov <ast@kernel.org>,
Vlastimil Babka <vbabka@suse.cz>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/1] local_lock: Minor improvements of local_trylock*() documentation
Date: Mon, 12 May 2025 12:41:15 +0200 [thread overview]
Message-ID: <20250512104115.KcF7Ct_u@linutronix.de> (raw)
In-Reply-To: <20250505170244.253170-1-leobras@redhat.com>
On 2025-05-05 14:02:44 [-0300], Leonardo Bras wrote:
> Fix local_trylock_init() documentation, as it was mentioning the non-try
> helper instead, and use the opportunity to make clear the try_lock*() needs
> to receive a local_trylock_t variable as parameter.
>
> Signed-off-by: Leonardo Bras <leobras@redhat.com>
…
> --- a/include/linux/local_lock.h
> +++ b/include/linux/local_lock.h
> @@ -45,38 +45,38 @@
> /**
> * local_unlock_irqrestore - Release a per CPU local lock and restore
> * interrupt flags
> * @lock: The lock variable
> * @flags: Interrupt flags to restore
> */
> #define local_unlock_irqrestore(lock, flags) \
> __local_unlock_irqrestore(lock, flags)
>
> /**
> - * local_lock_init - Runtime initialize a lock instance
> + * local_trylock_init - Runtime initialize a local_trylock instance
If you replace "lock instance" please use local_trylock_t instead
"local_trylock"
Other than that,
Reviewed-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
> */
> #define local_trylock_init(lock) __local_trylock_init(lock)
…
Sebastian
next prev parent reply other threads:[~2025-05-12 10:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-05 17:02 Leonardo Bras
2025-05-12 10:41 ` Sebastian Andrzej Siewior [this message]
2025-05-21 17:40 ` Leonardo Bras Soares Passos
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=20250512104115.KcF7Ct_u@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=ast@kernel.org \
--cc=kuba@kernel.org \
--cc=leobras@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=vbabka@suse.cz \
/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®