linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Palmer Dabbelt <palmer@dabbelt.com>
To: linux-pci@vger.kernel.org
To: linux-kernel@vger.kernel.org
To: bhelgaas@google.com
To: hch@infradead.org
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-snps-arc@lists.infradead.org
Cc: linux-cris-kernel@axis.com
Cc: linux-ia64@vger.kernel.org
Cc: linux-s390@vger.kernel.org
Cc: linux-sh@vger.kernel.org
Cc: sparclinux@vger.kernel.org
Subject: pci: Add generic pcibios_{fixup_bus,align_resource}
Date: Fri, 23 Jun 2017 18:50:41 -0700	[thread overview]
Message-ID: <20170624015044.16746-1-palmer@dabbelt.com> (raw)

While upstreaming the RISC-V port, it was pointed out that multiple
architectures have copied the mostly empty versions of at least one of these
functions.  This defines weakly bound versions of the common functions and
removes the now obselete functions from other ports.

This has been split out from the RISC-V submission so we can decouple all these
generic changes from our port review process.  There's some discussion on an
earlier version of the patch here

  https://lkml.org/lkml/2017/6/6/998

but I'm afraid a lot of this is really out of my wheelhouse (and I'm pretty
slammed trying to get the RISC-V port in better shape), so I'm afraid I'm not
going to be able to perform the full cleanup suggested.

             reply	other threads:[~2017-06-24  2:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-24  1:50 Palmer Dabbelt [this message]
2017-06-24  1:50 ` [PATCH 1/3] pci: Add a generic, weakly-linked pcibios_fixup_bus Palmer Dabbelt
2017-06-24  9:34   ` Geert Uytterhoeven
2017-06-24 21:32     ` Palmer Dabbelt
2017-06-24  1:50 ` [PATCH 2/3] pci: Add a generic, weakly-linked pcibios_align_resource Palmer Dabbelt
2017-06-24  9:41   ` Geert Uytterhoeven
2017-06-24 21:32     ` Palmer Dabbelt
2017-06-24  1:50 ` [PATCH 3/3] arc: kernel/pcibios.c is empty, delete it Palmer Dabbelt
2017-08-02 20:00 ` pci: Add generic pcibios_{fixup_bus,align_resource} Bjorn Helgaas

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=20170624015044.16746-1-palmer@dabbelt.com \
    --to=palmer@dabbelt.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-snps-arc@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).