From: "Marc - A. Dahlhaus [ Administration | Westermann GmbH ]" <mad@wol.de>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: pv_ops dom0 x86_32 PAE kernel buildlog of missingsymbols...
Date: Wed, 17 Dec 2008 17:32:06 +0100 [thread overview]
Message-ID: <1229531526.7033.24.camel@marc> (raw)
In-Reply-To: <1229529337.25701.106.camel@zakaz.uk.xensource.com>
Am Mittwoch, den 17.12.2008, 15:55 +0000 schrieb Ian Campbell:
> On Wed, 2008-12-17 at 16:49 +0100, Marc - A. Dahlhaus [ Administration |
> Westermann GmbH ] wrote:
> > Hello Jan,
> > hello Ian,
> >
> >
> > i did another build today (c/s 2239) and can confirm that only the
> > following two warnings are left:
> >
> > ERROR: "blk_put_queue" [drivers/xen/blkback/blkbk.ko] undefined!
> > ERROR: "blk_get_queue" [drivers/xen/blkback/blkbk.ko] undefined!
> >
> > Should i give Jan's patch a try or is another patch to address this
> > errors planed to be added to the patchset soon?
>
> I say just make these symbols EXPORT_SYMBOL_GPL or build blkback
> statically for the time being.
Used EXPORT_SYMBOL as remainder of exports in file used the same...
Build went silently of course.
> The exports were removed upstream because there was no in-tree module
> users but if we are adding one then reverting that could be acceptable.
> If that turns out to be unacceptable upstream then we could consider
> Jan's patch.
>
> Ian.
Thanks for the hint.
Marc
next prev parent reply other threads:[~2008-12-17 16:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-10 21:07 pv_ops dom0 x86_32 PAE kernel buildlog of missing symbols Marc - A. Dahlhaus
2008-12-11 12:00 ` Ian Campbell
2008-12-11 13:19 ` pv_ops dom0 x86_32 PAE kernel buildlog of missingsymbols Jan Beulich
2008-12-17 15:49 ` Marc - A. Dahlhaus [ Administration | Westermann GmbH ]
2008-12-17 15:55 ` Ian Campbell
2008-12-17 16:32 ` Marc - A. Dahlhaus [ Administration | Westermann GmbH ] [this message]
2008-12-17 16:45 ` Ian Campbell
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=1229531526.7033.24.camel@marc \
--to=mad@wol.de \
--cc=Ian.Campbell@citrix.com \
--cc=xen-devel@lists.xensource.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.