From: Matthew Wilcox <matthew@wil.cx>
To: linux-kernel@vger.kernel.org
Cc: Jens Axboe <jaxboe@fusionio.com>
Subject: xen_biovec_phys_mergeable not exported
Date: Tue, 20 Sep 2011 14:25:53 -0600 [thread overview]
Message-ID: <20110920202553.GB16740@parisc-linux.org> (raw)
In my NVMe driver, I call BIOVEC_PHYS_MERGEABLE(). If CONFIG_XEN
is defined, it references xen_biovec_phys_mergeable() which is not
EXPORT_SYMBOL. I think BIOVEC_PHYS_MERGABLE is a perfectly kosher thing
to be calling from a module that implements a bio-based block driver,
so I think the right thing to do is to add an EXPORT_SYMBOL(_GPL?) to
the Xen code when I submit the driver.
Does anyone have a different opinion on this?
--
Matthew Wilcox Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next reply other threads:[~2011-09-20 20:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-20 20:25 Matthew Wilcox [this message]
2011-09-21 12:09 ` xen_biovec_phys_mergeable not exported Jens Axboe
2011-09-21 18:46 ` Konrad Rzeszutek Wilk
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=20110920202553.GB16740@parisc-linux.org \
--to=matthew@wil.cx \
--cc=jaxboe@fusionio.com \
--cc=linux-kernel@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).