linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gerhard Sittig <gsi@denx.de>
To: linux-pci@vger.kernel.org, Jon Mason <jon.mason@intel.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>, Detlev Zundel <dzu@denx.de>,
	Gerhard Sittig <gsi@denx.de>
Subject: [PATCH RFC v1 3/4] ntb: prepare to build the 'data transport' as a separate module
Date: Wed,  6 Aug 2014 16:53:54 +0200	[thread overview]
Message-ID: <1407336835-30586-4-git-send-email-gsi@denx.de> (raw)
In-Reply-To: <1407336835-30586-1-git-send-email-gsi@denx.de>

Export those routines of the data transport which the PCI NTB hardware
drivers will reference, and provide module properties such that the data
transport over PCI NTB can build as a separate module.

This change does not alter the Makefile, the data transport still gets
statically linked against the driver for Intel hardware support.

Signed-off-by: Gerhard Sittig <gsi@denx.de>
---
 drivers/ntb/ntb_transport.c |    9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/drivers/ntb/ntb_transport.c b/drivers/ntb/ntb_transport.c
index 436326ad87bd..70f358c8cc09 100644
--- a/drivers/ntb/ntb_transport.c
+++ b/drivers/ntb/ntb_transport.c
@@ -61,7 +61,14 @@
 
 #include "ntb_hw.h"
 
+#define NTB_TRANSPORT_NAME	"Data transport over Non-Transparent Bridge"
 #define NTB_TRANSPORT_VERSION	3
+#define NTB_TRANSPORT_VERSTEXT	"3"
+
+MODULE_DESCRIPTION(NTB_TRANSPORT_NAME);
+MODULE_VERSION(NTB_TRANSPORT_VERSTEXT);
+MODULE_LICENSE("Dual BSD/GPL");
+MODULE_AUTHOR("Intel Corporation");
 
 static unsigned int transport_mtu = 0x401E;
 module_param(transport_mtu, uint, 0644);
@@ -979,6 +986,7 @@ err:
 	kfree(nt);
 	return rc;
 }
+EXPORT_SYMBOL(ntb_transport_init);
 
 void ntb_transport_free(void *transport)
 {
@@ -1009,6 +1017,7 @@ void ntb_transport_free(void *transport)
 	ntb_unregister_transport(ndev);
 	kfree(nt);
 }
+EXPORT_SYMBOL(ntb_transport_free);
 
 static void ntb_rx_copy_callback(void *data)
 {
-- 
1.7.10.4


  parent reply	other threads:[~2014-08-06 14:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-06 14:53 [PATCH RFC v1 0/4] PCI NTB: prepare for more hardware support Gerhard Sittig
2014-08-06 14:53 ` [PATCH RFC v1 1/4] ntb: split Intel specifics out of the "NTB hardware" interface Gerhard Sittig
2014-08-06 14:53 ` [PATCH RFC v1 2/4] ntb: header file nits (multiple inclusion, explicit entries) Gerhard Sittig
2014-08-06 14:53 ` Gerhard Sittig [this message]
2014-08-06 14:53 ` [PATCH RFC v1 4/4] ntb: de-couple data transport from hardware support Gerhard Sittig
2014-08-06 15:01 ` [PATCH RFC v1 0/4] PCI NTB: prepare for more " Gerhard Sittig
2014-08-18 16:24   ` Gerhard Sittig
2014-08-06 20:23 ` Rajat Jain
2014-08-11 10:11   ` Gerhard Sittig

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=1407336835-30586-4-git-send-email-gsi@denx.de \
    --to=gsi@denx.de \
    --cc=bhelgaas@google.com \
    --cc=dzu@denx.de \
    --cc=jon.mason@intel.com \
    --cc=linux-pci@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).