Linux-mm Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Rapoport <rppt@kernel.org>
To: Henry Elderman <henry.elderman.edu@gmail.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org,
	Henry Elderman <henry.elderman.edu+linux@gmail.com>
Subject: Re: [PATCH] mm/execmem: fix fallback_end description in kernel-doc
Date: Sun, 9 Aug 2026 08:52:21 +0300	[thread overview]
Message-ID: <angVlQGTvKecf-sP@kernel.org> (raw)
In-Reply-To: <20260807091958.4735-1-henry.elderman.edu+linux@gmail.com>

On Fri, Aug 07, 2026 at 11:19:58AM +0200, Henry Elderman wrote:
> The kernel-doc for struct execmem_range incorrectly describes @fallback_end
> as "start". Correct it to "end".
> 
> Signed-off-by: Henry Elderman <henry.elderman.edu+linux@gmail.com>

Reviewed-by: Mike Rapoport (Microsoft) <rppt@kernel.org>

> ---
>  include/linux/execmem.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/include/linux/execmem.h b/include/linux/execmem.h
> index 7de229134..1bd34925d 100644
> --- a/include/linux/execmem.h
> +++ b/include/linux/execmem.h
> @@ -89,7 +89,7 @@ static inline int execmem_restore_rox(void *ptr, size_t size) { return 0; }
>   * @end:	address space end (inclusive)
>   * @fallback_start: start of the secondary address space range for fallback
>   *                  allocations on architectures that require it
> - * @fallback_end:   start of the secondary address space (inclusive)
> + * @fallback_end:   end of the secondary address space (inclusive)
>   * @pgprot:	permissions for memory in this address space
>   * @alignment:	alignment required for text allocations
>   * @flags:	options for memory allocations for this range
> -- 
> 2.51.0
> 

-- 
Sincerely yours,
Mike.


      reply	other threads:[~2026-08-09  5:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-07  9:19 [PATCH] mm/execmem: fix fallback_end description in kernel-doc Henry Elderman
2026-08-09  5:52 ` Mike Rapoport [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=angVlQGTvKecf-sP@kernel.org \
    --to=rppt@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=henry.elderman.edu+linux@gmail.com \
    --cc=henry.elderman.edu@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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