From: Jesper Nilsson <jesper.nilsson@axis.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Jan Beulich <JBeulich@suse.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"mingo@elte.hu" <mingo@elte.hu>,
"tglx@linutronix.de" <tglx@linutronix.de>,
linux-cris-kernel <linux-cris-kernel@axis.com>,
"hpa@zytor.com" <hpa@zytor.com>
Subject: Re: [PATCH] x86/PCI: adjust section annotations
Date: Thu, 21 Jun 2012 17:53:27 +0200 [thread overview]
Message-ID: <20120621155327.GZ25226@axis.com> (raw)
In-Reply-To: <CAErSpo4yf66A-MoBLyUynMaha3Oa8_M2rNpwgK+2D1LgTaLhUw@mail.gmail.com>
On Thu, Jun 21, 2012 at 02:06:55AM +0200, Bjorn Helgaas wrote:
> On Mon, Jun 18, 2012 at 4:34 AM, Jan Beulich <JBeulich@suse.com> wrote:
> > DMI tables referenced from __init code only can be __initconst, and as
> > a result the functions referenced from there can become __init.
> >
> > pcibios_setup() can be __init as being a command line parsing function
> > only.
> >
> > A few other variables can then also have their attributes adjusted.
>
> This seems OK as far as it goes.
>
> However, if you're going to make pcibios_setup() __init for x86, I'd
> really encourage you to make it consistent across all the other
> architectures. And if you do *that*, I think it would be cool if you
> supplied a generic do-nothing "weak" version in the PCI core. That
> would allow you to remove it altogether from alpha, ia64, microblaze,
> mips pmc-sierra, parisc, powerpc, sh, sparc, tile, and xtensa.
>
> CRIS-folk: It would also fix what looks like a bug in cris, which
> implements pcibios_setup() such that pci_setup() doesn't even look for
> all the supposedly generic options.
Ok, thanks for the heads-up!
I'm going to take a look at the PCI code in the CRIS-port.
My current feeling is that the PCI support for CRIS probably
should be dropped, both due to rotted code, but also that the
hardware is hard to come by. I need to do some more digging around...
/^JN - Jesper Nilsson
--
Jesper Nilsson -- jesper.nilsson@axis.com
prev parent reply other threads:[~2012-06-21 15:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-18 10:34 [PATCH] x86/PCI: adjust section annotations Jan Beulich
2012-06-21 0:06 ` Bjorn Helgaas
2012-06-21 9:22 ` Jan Beulich
2012-06-21 14:19 ` Bjorn Helgaas
2012-06-21 14:24 ` H. Peter Anvin
2012-06-21 15:03 ` Jan Beulich
2012-06-21 15:53 ` Bjorn Helgaas
2012-06-21 15:53 ` Jesper Nilsson [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=20120621155327.GZ25226@axis.com \
--to=jesper.nilsson@axis.com \
--cc=JBeulich@suse.com \
--cc=bhelgaas@google.com \
--cc=hpa@zytor.com \
--cc=linux-cris-kernel@axis.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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