From: Mike Rapoport <rppt@kernel.org>
To: Pratyush Yadav <pratyush@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Alexander Graf <graf@amazon.com>,
Pasha Tatashin <pasha.tatashin@soleen.com>,
kexec@lists.infradead.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: add test_kho to KHO's entry
Date: Wed, 19 Nov 2025 09:14:56 +0200 [thread overview]
Message-ID: <aR1ucHaX8z9qV_oi@kernel.org> (raw)
In-Reply-To: <20251118182416.70660-1-pratyush@kernel.org>
On Tue, Nov 18, 2025 at 07:24:15PM +0100, Pratyush Yadav wrote:
> Commit b753522bed0b7 ("kho: add test for kexec handover") introduced the
> KHO test but missed adding it to KHO's MAINTAINERS entry. Add it so the
> KHO maintainers can get patches for its test.
>
> Cc: stable@vger.kernel.org
> Fixes: b753522bed0b7 ("kho: add test for kexec handover")
> Signed-off-by: Pratyush Yadav <pratyush@kernel.org>
Reviewed-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
> ---
> MAINTAINERS | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 05e336174ede5..b0873f8ebcda6 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -13799,6 +13799,7 @@ F: Documentation/admin-guide/mm/kho.rst
> F: Documentation/core-api/kho/*
> F: include/linux/kexec_handover.h
> F: kernel/liveupdate/kexec_handover*
> +F: lib/test_kho.c
> F: tools/testing/selftests/kho/
>
> KEYS-ENCRYPTED
> --
> 2.47.3
>
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2025-11-19 7:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-18 18:24 [PATCH] MAINTAINERS: add test_kho to KHO's entry Pratyush Yadav
2025-11-18 18:35 ` Pasha Tatashin
2025-11-19 7:14 ` Mike Rapoport [this message]
2025-11-19 7:36 ` Greg KH
2025-11-19 15:55 ` Pratyush Yadav
2025-11-19 16:02 ` Greg KH
2025-11-20 9:25 ` Pratyush Yadav
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=aR1ucHaX8z9qV_oi@kernel.org \
--to=rppt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=graf@amazon.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pasha.tatashin@soleen.com \
--cc=pratyush@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.