All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@davemloft.net>
To: mroos@linux.ee
Cc: sparclinux@vger.kernel.org, James.Bottomley@SteelEye.com,
	linux-scsi@vger.kernel.org
Subject: Re: 2.6.17-rc1+git, Sym2: unknown symbol pcibios_resource_to_bus (fwd)
Date: Mon, 17 Apr 2006 13:17:05 -0700 (PDT)	[thread overview]
Message-ID: <20060417.131705.40072804.davem@davemloft.net> (raw)
In-Reply-To: <Pine.SOC.4.61.0604171849100.21709@math.ut.ee>

From: Meelis Roos <mroos@linux.ee>
Date: Mon, 17 Apr 2006 18:49:41 +0300 (EEST)

Putting linux-scsi and James back on the CC:

> Forwarded from linux-scsi.
 ...
> pcibios_resource_to_bus is a new function which is inline in
> asm-generic/pci.h.   However, sparc64 overrides it as an external
> function which is in arch/sparc64/kernel/pci.c, so this looks like some
> type of sparc issue.

Why does the SYM2 driver possible even need this symbol?
That's what I'd like to have explained.

When this slipped into the Ubuntu kernel, I pushed back on it because
the usage was bogus, and I fear this is the same exact thing rearing
it's ugly head.

There is no reason to export this symbol outside of the generic PCI
code, which does not require a module symbol export.

WARNING: multiple messages have this Message-ID (diff)
From: "David S. Miller" <davem@davemloft.net>
To: mroos@linux.ee
Cc: sparclinux@vger.kernel.org, James.Bottomley@SteelEye.com,
	linux-scsi@vger.kernel.org
Subject: Re: 2.6.17-rc1+git, Sym2: unknown symbol pcibios_resource_to_bus
Date: Mon, 17 Apr 2006 20:17:05 +0000	[thread overview]
Message-ID: <20060417.131705.40072804.davem@davemloft.net> (raw)
In-Reply-To: <Pine.SOC.4.61.0604171849100.21709@math.ut.ee>

From: Meelis Roos <mroos@linux.ee>
Date: Mon, 17 Apr 2006 18:49:41 +0300 (EEST)

Putting linux-scsi and James back on the CC:

> Forwarded from linux-scsi.
 ...
> pcibios_resource_to_bus is a new function which is inline in
> asm-generic/pci.h.   However, sparc64 overrides it as an external
> function which is in arch/sparc64/kernel/pci.c, so this looks like some
> type of sparc issue.

Why does the SYM2 driver possible even need this symbol?
That's what I'd like to have explained.

When this slipped into the Ubuntu kernel, I pushed back on it because
the usage was bogus, and I fear this is the same exact thing rearing
it's ugly head.

There is no reason to export this symbol outside of the generic PCI
code, which does not require a module symbol export.

  reply	other threads:[~2006-04-17 20:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-17 15:49 2.6.17-rc1+git, Sym2: unknown symbol pcibios_resource_to_bus Meelis Roos
2006-04-17 20:17 ` David S. Miller [this message]
2006-04-17 20:17   ` David S. Miller
2006-04-17 20:26   ` 2.6.17-rc1+git, Sym2: unknown symbol pcibios_resource_to_bus (fwd) David S. Miller
2006-04-17 20:26     ` 2.6.17-rc1+git, Sym2: unknown symbol pcibios_resource_to_bus David S. Miller
2006-04-19  3:59     ` 2.6.17-rc1+git, Sym2: unknown symbol pcibios_resource_to_bus (fwd) Matthew Wilcox
2006-04-19  3:59       ` Matthew Wilcox
2006-04-19  4:02       ` David S. Miller
2006-04-19  4:02         ` 2.6.17-rc1+git, Sym2: unknown symbol pcibios_resource_to_bus David S. Miller

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=20060417.131705.40072804.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=James.Bottomley@SteelEye.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mroos@linux.ee \
    --cc=sparclinux@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 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.