From: Heiko Carstens <hca@linux.ibm.com>
To: Christian Borntraeger <borntraeger@linux.ibm.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>, KVM <kvm@vger.kernel.org>,
Janosch Frank <frankja@linux.ibm.com>,
Claudio Imbrenda <imbrenda@linux.ibm.com>,
David Hildenbrand <david@redhat.com>,
linux-s390 <linux-s390@vger.kernel.org>,
Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Janis Schoetterl-Glausch <scgl@linux.ibm.com>,
Thomas Huth <thuth@redhat.com>
Subject: Re: [GIT PULL 0/1] KVM: s390: Fix lockdep issue in vm memop
Date: Mon, 2 May 2022 19:58:14 +0200 [thread overview]
Message-ID: <YnAbtskXVQP11AkF@osiris> (raw)
In-Reply-To: <249d0100-fa58-bf48-b1d2-f28e94c3a5f2@linux.ibm.com>
On Mon, May 02, 2022 at 05:41:13PM +0200, Christian Borntraeger wrote:
> Am 02.05.22 um 17:39 schrieb Paolo Bonzini:
> > On 5/2/22 17:30, Christian Borntraeger wrote:
> > > Paolo,
> > >
> > > one patch that is sitting already too long in my tree (sorry, was out of
> > > office some days).
> >
> > Hi Christian,
> >
> > at this point I don't have much waiting for 5.18. Feel free to send it through the s390 tree.
>
> OK.
>
> Heiko, Vasily, can you queue this for your next pull request?
>
> Acked-by: Christian Borntraeger <borntraeger@de.ibm.com>
> for carrying this via the s390 tree.
It's now on the fixes branch:
https://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git/log/?h=fixes
Actually I was waiting if some fixes would come in, since the fixes
branch also had only one small fix until now.
prev parent reply other threads:[~2022-05-02 17:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 15:30 [GIT PULL 0/1] KVM: s390: Fix lockdep issue in vm memop Christian Borntraeger
2022-05-02 15:30 ` [GIT PULL 1/1] " Christian Borntraeger
2022-05-02 15:39 ` [GIT PULL 0/1] " Paolo Bonzini
2022-05-02 15:41 ` Christian Borntraeger
2022-05-02 17:58 ` Heiko Carstens [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=YnAbtskXVQP11AkF@osiris \
--to=hca@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=scgl@linux.ibm.com \
--cc=thuth@redhat.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.