From: Waiman Long <llong@redhat.com>
To: Suren Baghdasaryan <surenb@google.com>, akpm@linux-foundation.org
Cc: sfr@canb.auug.org.au, peterz@infradead.org, mingo@redhat.com,
will@kernel.org, boqun.feng@gmail.com, Liam.Howlett@Oracle.com,
david@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] seqlock: add missing parameter documentation for raw_seqcount_try_begin()
Date: Thu, 16 Jan 2025 14:28:26 -0500 [thread overview]
Message-ID: <2c6d1945-aa88-4658-a623-caf5165771b2@redhat.com> (raw)
In-Reply-To: <20250116182730.801497-1-surenb@google.com>
On 1/16/25 1:27 PM, Suren Baghdasaryan wrote:
> Add missing documentation for raw_seqcount_try_begin() start parameter.
>
> Fixes: dba4761a3e40 ("seqlock: add raw_seqcount_try_begin")
> Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
> Closes: https://lore.kernel.org/all/20250116170522.23e884d5@canb.auug.org.au/
> Signed-off-by: Suren Baghdasaryan <surenb@google.com>
> ---
> Applies over mm-unstable
>
> include/linux/seqlock.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/include/linux/seqlock.h b/include/linux/seqlock.h
> index 22c2c48b4265..b783a3a7ed62 100644
> --- a/include/linux/seqlock.h
> +++ b/include/linux/seqlock.h
> @@ -322,6 +322,7 @@ SEQCOUNT_LOCKNAME(mutex, struct mutex, true, mutex)
> * raw_seqcount_try_begin() - begin a seqcount_t read critical section
> * w/o lockdep and w/o counter stabilization
> * @s: Pointer to seqcount_t or any of the seqcount_LOCKNAME_t variants
> + * @start: count to be passed to read_seqcount_retry()
> *
> * Similar to raw_seqcount_begin(), except it enables eliding the critical
> * section entirely if odd, instead of doing the speculation knowing it will
>
> base-commit: 4637fa5d47a49c977116321cc575ea22215df22d
Acked-by: Waiman Long <longman@redhat.com>
The tip tree also has the "seqlock: add raw_seqcount_try_begin" commit
with a different hash - 96450ead1652.
Cheers, Longman
next prev parent reply other threads:[~2025-01-16 19:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-16 18:27 Suren Baghdasaryan
2025-01-16 19:28 ` Waiman Long [this message]
2025-01-16 22:03 ` Andrew Morton
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=2c6d1945-aa88-4658-a623-caf5165771b2@redhat.com \
--to=llong@redhat.com \
--cc=Liam.Howlett@Oracle.com \
--cc=akpm@linux-foundation.org \
--cc=boqun.feng@gmail.com \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=surenb@google.com \
--cc=will@kernel.org \
/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®