From: Matthew Wilcox <willy@linux.intel.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: pci tree build failure
Date: Mon, 29 Jun 2009 19:24:53 -0700 [thread overview]
Message-ID: <20090630022453.GE24061@linux.intel.com> (raw)
In-Reply-To: <20090629191324.5c86bbc0@jbarnes-g45>
On Mon, Jun 29, 2009 at 07:13:24PM -0700, Jesse Barnes wrote:
> On Tue, 30 Jun 2009 12:07:27 +1000
> Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> > Hi Jesse,
> >
> > Today's linux-next build (x86_64 allmodconfig) failed like this:
> >
> > ERROR: "pci_claim_resource" [drivers/pcmcia/yenta_socket.ko]
> > undefined!
> >
> > Caused by commit 6bb04b65dbff5a5bb01617351dbb0af577084752 ("yenta: Use
> > pci_claim_resource"). yenta can be built as a module, but
> > pci_claim_resource is not exported ...
> >
> > I have used the pci tree from next-20090629 for today.
>
> Damn, thought I built that. linux-next earns its keep yet again.
Sorry about that. I thought I'd checked that. Must have been confused
with another function. There do seem to be legitimate *drivers*
that could use it (i2o for one), so I propose making it a full-bodied
'EXPORT_SYMBOL' and not bother with the _GPL tag. Thoughts?
next prev parent reply other threads:[~2009-06-30 2:24 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-30 2:07 linux-next: pci tree build failure Stephen Rothwell
2009-06-30 2:13 ` Jesse Barnes
2009-06-30 2:24 ` Matthew Wilcox [this message]
2009-06-30 20:31 ` 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-10-07 1:38 Stephen Rothwell
2009-10-07 1:45 ` Tejun Heo
2009-10-07 15:39 ` Jesse Barnes
2009-07-15 1:45 Stephen Rothwell
2009-07-15 16:09 ` Jesse Barnes
2009-07-15 23:46 ` Stephen Rothwell
2009-03-23 1:49 Stephen Rothwell
2009-03-25 1:21 ` Stephen Rothwell
2009-03-25 1:38 ` Jesse Barnes
2009-03-25 3:41 ` Stephen Rothwell
2009-03-25 4:30 ` Matthew Wilcox
2009-03-25 15:55 ` Jesse Barnes
2009-03-26 3:05 ` Stephen Rothwell
2009-03-26 3:37 ` Jesse Barnes
2009-03-26 4:54 ` Stephen Rothwell
2008-10-22 2:39 Stephen Rothwell
2008-10-22 3:47 ` Jesse Barnes
2008-10-16 3:41 Stephen Rothwell
2008-10-16 3:44 ` Benjamin Herrenschmidt
2008-10-16 4:23 ` Jesse Barnes
2008-10-16 4:28 ` Benjamin Herrenschmidt
2008-10-18 22:41 ` Jesse Barnes
2008-10-19 4:15 ` Stephen Rothwell
2008-10-19 4:30 ` Jesse Barnes
[not found] <20080717130924.edd5a501.sfr@canb.auug.org.au>
2008-07-17 22:57 ` Rafael J. Wysocki
2008-07-18 6:09 ` Stephen Rothwell
2008-07-18 7:53 ` Ingo Molnar
2008-07-08 1:40 Stephen Rothwell
2008-07-08 14:54 ` Rafael J. Wysocki
[not found] <20080630142314.34654d3c.sfr@canb.auug.org.au>
2008-06-30 14:11 ` Alan Stern
2008-07-02 2:11 ` Jesse Barnes
2008-06-30 5:11 Stephen Rothwell
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=20090630022453.GE24061@linux.intel.com \
--to=willy@linux.intel.com \
--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 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.