From: Vipin Sharma <vipinsh@google.com>
To: Mike Rapoport <rppt@kernel.org>
Cc: pasha.tatashin@soleen.com, pratyush@kernel.org,
tarunsahu@google.com, skhawaja@google.com, shuah@kernel.org,
dmatlack@google.com, linux-kernel@vger.kernel.org,
kexec@lists.infradead.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v3 0/2] Make liveupdate selftests library
Date: Wed, 17 Jun 2026 12:08:25 -0700 [thread overview]
Message-ID: <20260617190754.GC2704872.vipinsh@google.com> (raw)
In-Reply-To: <ajLtfkuMP4DEGlqe@kernel.org>
On Wed, Jun 17, 2026 at 09:54:54PM +0300, Mike Rapoport wrote:
> Hi Vipin,
>
> On Fri, Jun 12, 2026 at 02:45:10PM -0700, Vipin Sharma wrote:
> > Hello,
> >
> > This is v3 series of refactoring liveupdate selftests as a library. It
> > exposes common liveupdate ioctls as a library which can be used by other
> > selftests like VFIO and IOMMU.
>
> Let's revisit this after -rc1 is out.
> I don't think there would a need to change anything, it's just the matter
> of applying the patches to the right base :)
Sounds good, thank you!
>
> > Currently, there are no users of this change but it is being used in
> > VFIO and iommu liveupdate series.
>
> --
> Sincerely yours,
> Mike.
prev parent reply other threads:[~2026-06-17 19:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-12 21:45 [PATCH v3 0/2] Make liveupdate selftests library Vipin Sharma
2026-06-12 21:45 ` [PATCH v3 1/2] selftests/liveupdate: Use luo_test_utils.c for liveupdate ioctl APIs Vipin Sharma
2026-06-12 21:45 ` [PATCH v3 2/2] selftests/liveupdate: Move luo_test_utils.* into a reusable library Vipin Sharma
2026-06-14 12:45 ` Pasha Tatashin
2026-06-17 18:54 ` [PATCH v3 0/2] Make liveupdate selftests library Mike Rapoport
2026-06-17 19:08 ` Vipin Sharma [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=20260617190754.GC2704872.vipinsh@google.com \
--to=vipinsh@google.com \
--cc=dmatlack@google.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=pasha.tatashin@soleen.com \
--cc=pratyush@kernel.org \
--cc=rppt@kernel.org \
--cc=shuah@kernel.org \
--cc=skhawaja@google.com \
--cc=tarunsahu@google.com \
/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.