Linux Documentation
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Manuel Ebner <manuelebner@mailbox.org>,
	Matthew Wilcox <willy@infradead.org>,
	Jonathan Corbet <corbet@lwn.net>,
	Shuah Khan <skhan@linuxfoundation.org>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] errseq: add missing bracket
Date: Thu, 9 Jul 2026 09:07:50 -0700	[thread overview]
Message-ID: <6bf7fae9-9b77-4970-87a2-2ef5da049656@infradead.org> (raw)
In-Reply-To: <20260709092900.380694-1-manuelebner@mailbox.org>



On 7/9/26 2:28 AM, Manuel Ebner wrote:
> Add missing ')' to nested functions of code block.
> 
> Signed-off-by: Manuel Ebner <manuelebner@mailbox.org>

Acked-by: Randy Dunlap <rdunlap@infradead.org>
Thanks.

> ---
>  Documentation/core-api/errseq.rst | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/Documentation/core-api/errseq.rst b/Documentation/core-api/errseq.rst
> index ff332e272405..d298d4cd2f60 100644
> --- a/Documentation/core-api/errseq.rst
> +++ b/Documentation/core-api/errseq.rst
> @@ -143,7 +143,7 @@ Because of this, it's often advantageous to first do an errseq_check to
>  see if anything has changed, and only later do an
>  errseq_check_and_advance after taking the lock. e.g.::
>  
> -        if (errseq_check(&wd.wd_err, READ_ONCE(su.s_wd_err)) {
> +        if (errseq_check(&wd.wd_err, READ_ONCE(su.s_wd_err))) {
>                  /* su.s_wd_err is protected by s_wd_err_lock */
>                  spin_lock(&su.s_wd_err_lock);
>                  err = errseq_check_and_advance(&wd.wd_err, &su.s_wd_err);

-- 
~Randy

  reply	other threads:[~2026-07-09 16:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-09  9:28 [PATCH] errseq: add missing bracket Manuel Ebner
2026-07-09 16:07 ` Randy Dunlap [this message]
2026-07-10 19:04 ` 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=6bf7fae9-9b77-4970-87a2-2ef5da049656@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manuelebner@mailbox.org \
    --cc=skhan@linuxfoundation.org \
    --cc=willy@infradead.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