From: Tejun Heo <tj@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: pci tree build failure
Date: Wed, 07 Oct 2009 10:45:35 +0900 [thread overview]
Message-ID: <4ACBF2BF.5060707@kernel.org> (raw)
In-Reply-To: <20091007123821.043465c6.sfr@canb.auug.org.au>
Stephen Rothwell wrote:
> Hi Jesse,
>
> Today's linux-next build (x86_64 allmodconfig) failed like this:
>
> ERROR: "pci_set_cacheline_size" [drivers/pcmcia/pcmcia_core.ko] undefined!
>
> Caused by commit 018bc96e8e27bfcafec9357ff370bf51241a7ea7 ("pccard:
> configure CLS on attach") which neglected to EXPORT_SYMBOL
> pci_set_cacheline_size.
>
> I have used the version of the pci tree from next-20091006 for today.
>
Oops, Jesse, can you please add EXPORT_SYMBOL_GPL() there?
Thanks.
--
tejun
next prev parent reply other threads:[~2009-10-07 1:46 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-07 1:38 linux-next: pci tree build failure Stephen Rothwell
2009-10-07 1:45 ` Tejun Heo [this message]
2009-10-07 15:39 ` Jesse Barnes
-- strict thread matches above, loose matches on Subject: below --
2010-01-27 6:49 Stephen Rothwell
2010-01-27 17:31 ` Jesse Barnes
2010-01-28 6:14 ` Stephen Rothwell
2010-01-18 8:40 Stephen Rothwell
2010-01-18 21:24 ` Rafael J. Wysocki
2010-01-19 2:35 ` Jesse Barnes
2010-01-19 3:19 ` Stephen Rothwell
2010-01-20 4:39 ` Jesse Barnes
2010-01-20 5:19 ` Stephen Rothwell
2010-01-04 22:55 Stephen Rothwell
2010-01-04 23:10 ` Matthew Wilcox
2010-01-04 23:48 ` Jesse Barnes
2010-01-05 3:41 ` Stephen Rothwell
2009-07-15 1:45 Stephen Rothwell
2009-07-15 16:09 ` Jesse Barnes
2009-07-15 23:46 ` Stephen Rothwell
2009-06-30 2:07 Stephen Rothwell
2009-06-30 2:13 ` Jesse Barnes
2009-06-30 2:24 ` Matthew Wilcox
2009-06-30 20:31 ` Jesse Barnes
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=4ACBF2BF.5060707@kernel.org \
--to=tj@kernel.org \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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