From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Fabiano Rosas <farosas@linux.ibm.com>, kvm-ppc@vger.kernel.org
Cc: aik@ozlabs.ru, linuxppc-dev@lists.ozlabs.org, npiggin@gmail.com
Subject: Re: [PATCH v3 0/4] KVM: PPC: KVM module exit fixes
Date: Sat, 12 Mar 2022 10:37:26 +0000 [thread overview]
Message-ID: <164708144610.832402.1913966629226492244.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <20220125155735.1018683-1-farosas@linux.ibm.com>
On Tue, 25 Jan 2022 12:57:31 -0300, Fabiano Rosas wrote:
> changes from v2:
>
> - patch 4: Matched module_put() to try_module_get()
>
> v2:
> https://lore.kernel.org/r/20220124220803.1011673-1-farosas@linux.ibm.com
>
> [...]
Applied to powerpc/topic/ppc-kvm.
[1/4] KVM: PPC: Book3S HV: Check return value of kvmppc_radix_init
https://git.kernel.org/powerpc/c/69ab6ac380a00244575de02c406dcb9491bf3368
[2/4] KVM: PPC: Book3S HV: Delay setting of kvm ops
https://git.kernel.org/powerpc/c/c5d0d77b45265905bba2ce6e63c9a02bbd11c43c
[3/4] KVM: PPC: Book3S HV: Free allocated memory if module init fails
https://git.kernel.org/powerpc/c/175be7e5800e2782a7e38ee9e1b64633494c4b44
[4/4] KVM: PPC: Decrement module refcount if init_vm fails
https://git.kernel.org/powerpc/c/4feb74aa64b35b21a4937f96d7a940adee286e5b
cheers
prev parent reply other threads:[~2022-03-12 10:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-25 15:57 [PATCH v3 0/4] KVM: PPC: KVM module exit fixes Fabiano Rosas
2022-01-25 15:57 ` [PATCH v3 1/4] KVM: PPC: Book3S HV: Check return value of kvmppc_radix_init Fabiano Rosas
2022-01-25 15:57 ` [PATCH v3 2/4] KVM: PPC: Book3S HV: Delay setting of kvm ops Fabiano Rosas
2022-01-25 15:57 ` [PATCH v3 3/4] KVM: PPC: Book3S HV: Free allocated memory if module init fails Fabiano Rosas
2022-01-25 15:57 ` [PATCH v3 4/4] KVM: PPC: Decrement module refcount if init_vm fails Fabiano Rosas
2022-03-12 10:37 ` Michael Ellerman [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=164708144610.832402.1913966629226492244.b4-ty@ellerman.id.au \
--to=patch-notifications@ellerman.id.au \
--cc=aik@ozlabs.ru \
--cc=farosas@linux.ibm.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).