From: Christoph Hellwig <hch@infradead.org>
To: Halil Pasic <pasic@linux.ibm.com>
Cc: kvm@vger.kernel.org, linux-s390@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Thiago Jung Bauermann <bauerman@linux.ibm.com>,
"Lendacky, Thomas" <Thomas.Lendacky@amd.com>,
Thomas Gleixner <tglx@linutronix.de>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Janosch Frank <frankja@linux.ibm.com>
Subject: Re: [PATCH 1/1] s390/protvirt: restore force_dma_unencrypted()
Date: Mon, 15 Jul 2019 06:20:27 -0700 [thread overview]
Message-ID: <20190715132027.GA18357@infradead.org> (raw)
In-Reply-To: <20190715131719.100650-1-pasic@linux.ibm.com>
This looks good to me - if you and Tom are fine with it I'd like to
fold it into his commit so that what I'll send to Linus is bisection
clean.
> Note: we still need sev_active() defined because of the reference
> in fs/core/vmcore, but this one is likely to go away soon along
> with the need for an s390 sev_active().
Any chance we could not change the return value from the function
at least in this patch/fold as that change seems unrelated to the
dma functionality. If that is what you really wanted and only
the dma code was in the way we can happily merge it as a separate
patch, of couse.
next prev parent reply other threads:[~2019-07-15 13:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-15 13:17 [PATCH 1/1] s390/protvirt: restore force_dma_unencrypted() Halil Pasic
2019-07-15 13:20 ` Christoph Hellwig [this message]
2019-07-15 13:28 ` Lendacky, Thomas
2019-07-15 13:29 ` Christoph Hellwig
2019-07-15 14:20 ` Christoph Hellwig
2019-07-15 14:25 ` Halil Pasic
2019-07-15 15:25 ` Lendacky, Thomas
2019-07-15 14:21 ` Halil Pasic
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=20190715132027.GA18357@infradead.org \
--to=hch@infradead.org \
--cc=Thomas.Lendacky@amd.com \
--cc=bauerman@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=frankja@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=pasic@linux.ibm.com \
--cc=tglx@linutronix.de \
/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 NNTP newsgroup(s).