From: Paolo Bonzini <pbonzini@redhat.com>
To: Heiko Carstens <hca@linux.ibm.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] s390 updates for 5.18-rc6
Date: Thu, 5 May 2022 14:46:22 +0200 [thread overview]
Message-ID: <8342100d-a9f6-2f6d-30d0-b3950661d0c6@redhat.com> (raw)
In-Reply-To: <YnPFjuBYZw/dj01U@osiris>
On 5/5/22 14:39, Heiko Carstens wrote:
> Hi Linus,
>
> please pull s390 updates for 5.18-rc6. Please note that this pull
> request includes two s390 specific kvm commits, which normally would
> have been routed via the kvm tree.
>
> Due to lack of other patches in the kvm tree Christian Borntraeger
> asked to get them upstream via the s390 tree:
> https://lore.kernel.org/linux-s390/249d0100-fa58-bf48-b1d2-f28e94c3a5f2@linux.ibm.com/
Needless to say, kvm patches have since materialized and I'll send a
pull request later this week.
But anyway s390 is the architecture where I expect zero issues if KVM
patches go in through arch maintainers. Compared to other
architectures, there are a lot more points of contact between KVM and
the rest of arch/s390; you know the KVM code well; and honestly the
whole architecture is mostly Amharic to me when it comes to the
privileged interface.
Thanks,
Paolo
next prev parent reply other threads:[~2022-05-05 12:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-05 12:39 Heiko Carstens
2022-05-05 12:46 ` Paolo Bonzini [this message]
2022-05-05 18:46 ` pr-tracker-bot
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=8342100d-a9f6-2f6d-30d0-b3950661d0c6@redhat.com \
--to=pbonzini@redhat.com \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®