From: James Bottomley <James.Bottomley@SteelEye.com>
To: Michael Ellerman <michael@ellerman.id.au>
Cc: Greg Kroah-Hartman <greg@kroah.com>,
linux-mips@linux-mips.org, dev-etrax@axis.com,
linux-ia64@vger.kernel.org, discuss@x86-64.org, chris@zankel.net,
dhowells@redhat.com, linuxppc-dev@ozlabs.org,
linux-m68k@vger.kernel.org, ink@jurassic.park.msu.ru,
gerg@uclinux.org, sparclinux@vger.kernel.org,
uclinux-v850@lsi.nec.co.jp, linux-pci@atrey.karlin.mff.cuni.cz,
parisc-linux@parisc-linux.org, kernel@wantstofly.org,
rth@twiddle.net
Subject: Re: [parisc-linux] [PATCH 1/2] Use a weak symbol for the empty
Date: Tue, 06 Mar 2007 18:01:00 +0000 [thread overview]
Message-ID: <1173204060.3379.28.camel@mulgrave.il.steeleye.com> (raw)
In-Reply-To: <1173193568.89821.610708199943.qpush@concordia>
On Tue, 2007-03-06 at 16:06 +0100, Michael Ellerman wrote:
> I'm not sure if this is going to fly, weak symbols work on the compilers I'm
> using, but whether they work for all of the affected architectures I can't say.
> I've cc'ed as many arch maintainers/lists as I could find.
Well, for your use, PCI already uses weak symbols, so it must work on
every architecture that you want to do it on ...
James
prev parent reply other threads:[~2007-03-06 18:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-06 15:06 [PATCH 1/2] Use a weak symbol for the empty version of pcibios_add_platform_entries() Michael Ellerman
2007-03-06 15:06 ` [PATCH 2/2] Make pcibios_add_platform_entries() return errors Michael Ellerman
2007-03-06 18:05 ` [parisc-linux] [PATCH 2/2] Make pcibios_add_platform_entries() James Bottomley
2007-03-07 8:55 ` Michael Ellerman
2007-03-06 18:01 ` James Bottomley [this message]
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=1173204060.3379.28.camel@mulgrave.il.steeleye.com \
--to=james.bottomley@steeleye.com \
--cc=chris@zankel.net \
--cc=dev-etrax@axis.com \
--cc=dhowells@redhat.com \
--cc=discuss@x86-64.org \
--cc=gerg@uclinux.org \
--cc=greg@kroah.com \
--cc=ink@jurassic.park.msu.ru \
--cc=kernel@wantstofly.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=linuxppc-dev@ozlabs.org \
--cc=michael@ellerman.id.au \
--cc=parisc-linux@parisc-linux.org \
--cc=rth@twiddle.net \
--cc=sparclinux@vger.kernel.org \
--cc=uclinux-v850@lsi.nec.co.jp \
/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