From: Linus Torvalds <torvalds@linux-foundation.org>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: [git pull] PCI changes for 2.6.30
Date: Wed, 1 Apr 2009 10:01:12 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.2.00.0904010957520.4130@localhost.localdomain> (raw)
In-Reply-To: <20090331121331.3673cf59@hobbes>
On Tue, 31 Mar 2009, Jesse Barnes wrote:
>
> Please consider pulling my PCI tree from
> git://git.kernel.org/pub/scm/linux/kernel/git/jbarnes/pci-2.6 linux-next
This produces
WARNING: drivers/built-in.o(.text+0x69a1): Section mismatch in reference from the function dev_rescan_store() to the function .devinit.text:pci_rescan_bus()
The function dev_rescan_store() references
the function __devinit pci_rescan_bus().
This is often because dev_rescan_store lacks a __devinit
annotation or the annotation of pci_rescan_bus is wrong.
Hmm?
> Anyway hope this pull is ok. I went through every warning by hand to make
> sure none were caused by PCI commits, but that was with the bits in this
> tree, which are -rc8 vintage.
You can tell it's rebased, but at least it's not rebased five minutes ago,
so I assume it has some testing. It's the "I just rebased a couple of
minutes before posting this 'please pull' message" that I find really
annoying, since it's so clear that the end result has no real testing at
all.
Linus
next prev parent reply other threads:[~2009-04-01 17:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-31 19:13 [git pull] PCI changes for 2.6.30 Jesse Barnes
2009-04-01 17:01 ` Linus Torvalds [this message]
2009-04-01 17:13 ` Jesse Barnes
2009-04-01 18:37 ` Alex Chiang
2009-04-01 19:12 ` Sam Ravnborg
2009-04-01 22:23 ` Alex Chiang
2009-04-05 19:34 ` Sam Ravnborg
2009-04-06 15:19 ` Alex Chiang
2009-04-06 19:16 ` Sam Ravnborg
2009-04-02 0:24 ` Alex Chiang
2009-04-06 18:46 ` 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=alpine.LFD.2.00.0904010957520.4130@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@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