All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: Martin Schwidefsky <schwidefsky@de.ibm.com>,
	Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: Farhan Ali <alifm@linux.ibm.com>,
	Eric Farman <farman@linux.ibm.com>,
	Halil Pasic <pasic@linux.ibm.com>,
	linux-s390@vger.kernel.org, kvm@vger.kernel.org,
	Cornelia Huck <cohuck@redhat.com>
Subject: [PULL 5/9] s390/cio: export hsch to modules
Date: Thu, 25 Apr 2019 11:15:55 +0200	[thread overview]
Message-ID: <20190425091559.15490-6-cohuck@redhat.com> (raw)
In-Reply-To: <20190425091559.15490-1-cohuck@redhat.com>

The vfio-ccw code will need this, and it matches treatment of ssch
and csch.

Reviewed-by: Pierre Morel <pmorel@linux.ibm.com>
Reviewed-by: Halil Pasic <pasic@linux.ibm.com>
Signed-off-by: Cornelia Huck <cohuck@redhat.com>
---
 drivers/s390/cio/ioasm.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/s390/cio/ioasm.c b/drivers/s390/cio/ioasm.c
index 14d328338ce2..08eb10283b18 100644
--- a/drivers/s390/cio/ioasm.c
+++ b/drivers/s390/cio/ioasm.c
@@ -233,6 +233,7 @@ int hsch(struct subchannel_id schid)
 
 	return ccode;
 }
+EXPORT_SYMBOL(hsch);
 
 static inline int __xsch(struct subchannel_id schid)
 {
-- 
2.17.2

  parent reply	other threads:[~2019-04-25  9:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-25  9:15 [PULL 0/9] vfio-ccw patches for 5.2 Cornelia Huck
2019-04-25  9:15 ` [PULL 1/9] vfio-ccw: make it safe to access channel programs Cornelia Huck
2019-04-25  9:15 ` [PULL 2/9] vfio-ccw: rework ssch state handling Cornelia Huck
2019-04-25  9:15 ` [PULL 3/9] vfio-ccw: protect the I/O region Cornelia Huck
2019-04-25  9:15 ` [PULL 4/9] vfio-ccw: add capabilities chain Cornelia Huck
2019-04-25  9:15 ` Cornelia Huck [this message]
2019-04-25  9:15 ` [PULL 6/9] vfio-ccw: add handling for async channel instructions Cornelia Huck
2019-04-25  9:15 ` [PULL 7/9] vfio-ccw: Do not call flush_workqueue while holding the spinlock Cornelia Huck
2019-04-25  9:15 ` [PULL 8/9] vfio-ccw: Release any channel program when releasing/removing vfio-ccw mdev Cornelia Huck
2019-04-25  9:15 ` [PULL 9/9] vfio-ccw: Prevent quiesce function going into an infinite loop Cornelia Huck
2019-04-25 11:47 ` [PULL 0/9] vfio-ccw patches for 5.2 Martin Schwidefsky

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=20190425091559.15490-6-cohuck@redhat.com \
    --to=cohuck@redhat.com \
    --cc=alifm@linux.ibm.com \
    --cc=farman@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=schwidefsky@de.ibm.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.