mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-pci@vger.kernel.org, linux-next@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>,
	Dexuan Cui <dexuan.cui@intel.com>
Subject: Re: linux-next: Tree for December 17 (pci/quirks)
Date: Thu, 17 Dec 2009 10:59:00 -0800	[thread overview]
Message-ID: <20091217105900.1d8b4f42@jbarnes-piketon> (raw)
In-Reply-To: <20091217095506.64f0a43f.randy.dunlap@oracle.com>

On Thu, 17 Dec 2009 09:55:06 -0800
Randy Dunlap <randy.dunlap@oracle.com> wrote:

> On Thu, 17 Dec 2009 16:58:40 +1100 Stephen Rothwell wrote:
> 
> > Hi all,
> > 
> > My usual call for calm: please do not put stuff destined for 2.6.34
> > into linux-next trees until after 2.6.33-rc1.
> > 
> > Changes since 20091216:
> 
> 
> When CONFIG_PCI_QUIRKS=n:
> 
> drivers/built-in.o: In function `pci_dev_reset':
> pci.c:(.text+0xdb0b): undefined reference to `pci_dev_reset_methods'
> pci.c:(.text+0xdb2b): undefined reference to `pci_dev_reset_methods'
> pci.c:(.text+0xdb85): undefined reference to `pci_dev_reset_methods'
> 
> 
> pci_dev_reset() calls (inlined) pci_dev_specific_reset(),
> which references pci_dev_reset_methods, which does not exist.

Dexuan, can you fix this up?

Thanks,
-- 
Jesse Barnes, Intel Open Source Technology Center

  reply	other threads:[~2009-12-17 19:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-17  5:58 linux-next: Tree for December 17 Stephen Rothwell
2009-12-17 17:55 ` linux-next: Tree for December 17 (pci/quirks) Randy Dunlap
2009-12-17 18:59   ` Jesse Barnes [this message]
2009-12-18  8:57     ` Cui, Dexuan
2009-12-17 17:57 ` linux-next: Tree for December 17 (media/dvb) Randy Dunlap
2009-12-18 10:50   ` Mauro Carvalho Chehab

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=20091217105900.1d8b4f42@jbarnes-piketon \
    --to=jbarnes@virtuousgeek.org \
    --cc=dexuan.cui@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --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

all inboxes | Powered by JetHome®