public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Carlos Llamas <cmllamas@google.com>
Cc: stable@vger.kernel.org, Mark Rutland <mark.rutland@arm.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Kees Cook <keescook@chromium.org>
Subject: Re: [PATCH 6.6.y] locking/atomic: scripts: fix ${atomic}_sub_and_test() kerneldoc
Date: Mon, 24 Jun 2024 17:03:26 +0200	[thread overview]
Message-ID: <2024062416-engine-client-8b0a@gregkh> (raw)
In-Reply-To: <20240620181805.2713680-1-cmllamas@google.com>

On Thu, Jun 20, 2024 at 06:18:05PM +0000, Carlos Llamas wrote:
> commit f92a59f6d12e31ead999fee9585471b95a8ae8a3 upstream.
> 
> For ${atomic}_sub_and_test() the @i parameter is the value to subtract,
> not add. Fix the typo in the kerneldoc template and generate the headers
> with this update.
> 
> Fixes: ad8110706f38 ("locking/atomic: scripts: generate kerneldoc comments")
> Suggested-by: Mark Rutland <mark.rutland@arm.com>
> Signed-off-by: Carlos Llamas <cmllamas@google.com>
> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
> Acked-by: Mark Rutland <mark.rutland@arm.com>
> Reviewed-by: Kees Cook <keescook@chromium.org>
> Cc: stable@vger.kernel.org
> Link: https://lkml.kernel.org/r/20240515133844.3502360-1-cmllamas@google.com
> [cmllamas: generate headers with gen-atomics.sh]
> Signed-off-by: Carlos Llamas <cmllamas@google.com>
> ---

Now queued up, thanks.

greg k-h

      reply	other threads:[~2024-06-24 15:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-18 13:25 FAILED: patch "[PATCH] locking/atomic: scripts: fix ${atomic}_sub_and_test()" failed to apply to 6.6-stable tree gregkh
2024-06-20 18:18 ` [PATCH 6.6.y] locking/atomic: scripts: fix ${atomic}_sub_and_test() kerneldoc Carlos Llamas
2024-06-24 15:03   ` Greg KH [this message]

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=2024062416-engine-client-8b0a@gregkh \
    --to=greg@kroah.com \
    --cc=cmllamas@google.com \
    --cc=keescook@chromium.org \
    --cc=mark.rutland@arm.com \
    --cc=peterz@infradead.org \
    --cc=stable@vger.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