linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Myron Stowe <mstowe@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Linus <torvalds@linux-foundation.org>
Subject: Re: linux-next: build failure after merge of the pci tree
Date: Tue, 25 Oct 2011 11:14:38 -0600	[thread overview]
Message-ID: <1319562878.2417.18.camel@zim.stowe> (raw)
In-Reply-To: <20111026004430.6725033af543cb336a786a3e@canb.auug.org.au>

On Wed, 2011-10-26 at 00:44 +1100, Stephen Rothwell wrote:
> Hi Jesse,
> 
> After merging the pci tree, today's linux-next build (powerpc
> pseries_defconfig) failed like this:
> 
> drivers/pci/pci.c:2605: error: redefinition of 'pcibios_set_master'
> arch/powerpc/include/asm/pci.h:49: note: previous definition of
> 'pcibios_set_master' was here
> 
> Presumably caused by commit 481da3e3d53e ("PCI: Pull PCI 'latency
> timer'
> setup up into the core").
> 
Yes, commit 481da3e3d53e is the culprit here.  I was trying to not
modify architectures that had inline nop functions but it's now obvious
that the compiler sees the architecture specific include files before it
sees the __weak def I added in drivers/pci/pci.c

I think the best approach here is to remove the inline versions of
pcibios_set_master() for the architectures with inline nops.  This will
effectively add the new generic code to those architectures; which will
be a slight change in behavior for them.  This has the benefit of ending
up with most architectures utilizing the new generic code and only those
that absolutely must having specific versions of pcibios_set_master()
that over-rides the generic __weak code.  If we encounter issues going
forward with this approach for a specific architecture then we can add a
non-weak empty version back in for it.

If anyone has issues with such an approach please let me know.  In the
mean time -

I'll work on modifying the patch series accordingly.

Jesse: can you drop the series from pci-2.6/linux-next and I'll re-post
with v2?

Stephen: do you need me to do anything here or can you also drop the
series from linux-next?

Myron

  reply	other threads:[~2011-10-25 17:14 UTC|newest]

Thread overview: 90+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-25 13:44 linux-next: build failure after merge of the pci tree Stephen Rothwell
2011-10-25 17:14 ` Myron Stowe [this message]
2011-10-25 19:58   ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2024-11-07 12:02 Stephen Rothwell
2024-11-07 12:07 ` Manivannan Sadhasivam
2024-11-07 13:13   ` Bjorn Helgaas
2024-07-01  3:01 Stephen Rothwell
2024-07-01 20:19 ` Krzysztof Wilczyński
2024-07-03  1:03   ` Krzysztof Wilczyński
2023-10-24  5:14 Stephen Rothwell
2023-10-24 11:01 ` Ilpo Järvinen
2023-10-23  0:05 Stephen Rothwell
2023-10-23  7:30 ` Yoshihiro Shimoda
2023-10-23  7:34   ` Krzysztof Wilczyński
2023-10-23  9:36     ` Yoshihiro Shimoda
2023-10-23 12:56       ` Krzysztof Wilczyński
2023-10-06  0:56 Stephen Rothwell
2023-10-06  1:23 ` Mario Limonciello
2023-10-06 14:11 ` Bjorn Helgaas
2023-01-15 22:53 Stephen Rothwell
2023-01-18 21:34 ` Bjorn Helgaas
2021-11-04 22:56 Stephen Rothwell
2021-10-17 22:55 Stephen Rothwell
2021-10-18 14:26 ` Bjorn Helgaas
2021-10-10 23:12 Stephen Rothwell
2021-10-11  5:37 ` Manivannan Sadhasivam
2021-10-11 11:22   ` Lorenzo Pieralisi
2020-08-03  1:36 Stephen Rothwell
2020-07-22  1:39 Stephen Rothwell
2020-03-13  1:54 Stephen Rothwell
2020-03-09 23:07 Stephen Rothwell
2020-03-10 19:10 ` Bjorn Helgaas
2019-08-30  3:23 Stephen Rothwell
2019-08-30 12:30 ` Bjorn Helgaas
2019-08-31  4:21   ` Vidya Sagar
2019-08-31  8:49     ` Lorenzo Pieralisi
2019-08-31 14:40       ` Bjorn Helgaas
2019-08-31 16:49       ` Vidya Sagar
2018-09-26  5:00 Stephen Rothwell
2018-09-26 14:25 ` Keith Busch
2018-09-26 14:58   ` Keith Busch
2018-09-26 19:48     ` Bjorn Helgaas
2018-09-26 21:27       ` Stephen Rothwell
2018-03-26  1:31 Stephen Rothwell
2018-03-26 19:53 ` Bjorn Helgaas
2018-03-27 16:53   ` Rob Herring
2018-01-31 23:51 Stephen Rothwell
2018-02-01  8:56 ` Niklas Cassel
2018-02-01 11:10   ` Lorenzo Pieralisi
2018-02-01 11:16     ` Niklas Cassel
2018-02-01 11:22       ` Kishon Vijay Abraham I
2018-02-01 11:29         ` Niklas Cassel
2018-02-01 19:00   ` Bjorn Helgaas
2018-02-01 21:13     ` Stephen Rothwell
2018-01-25  5:49 Stephen Rothwell
2018-01-25 13:55 ` Rob Herring
2018-01-25 14:58   ` Bjorn Helgaas
2018-01-29  4:41   ` Michael Ellerman
2016-04-26  1:13 Stephen Rothwell
2016-04-26 10:05 ` Joerg Roedel
2016-04-22  0:48 Stephen Rothwell
2016-01-11  1:42 Stephen Rothwell
2016-01-11  6:34 ` Bjorn Helgaas
2015-11-01 15:23 Stephen Rothwell
2015-11-02  0:00 ` Ley Foon Tan
2015-11-02 18:12   ` Bjorn Helgaas
2015-11-03  8:02     ` Ley Foon Tan
2015-11-02  0:09 ` Ley Foon Tan
2014-06-11  2:02 Stephen Rothwell
2014-06-11  2:23 ` Bjorn Helgaas
2014-05-22  4:09 Stephen Rothwell
2014-05-22  6:49 ` Sebastian Ott
2014-05-22 16:58   ` Bjorn Helgaas
2012-11-06  0:27 Stephen Rothwell
2012-11-06  1:55 ` Greg Kroah-Hartman
2012-11-06  2:09   ` Stephen Rothwell
2012-11-06 22:01 ` Bjorn Helgaas
2012-09-11  1:29 Stephen Rothwell
2012-09-11 14:28 ` Bjorn Helgaas
2012-02-13  2:21 Stephen Rothwell
2012-02-14 16:45 ` Jesse Barnes
2011-12-06  0:18 Stephen Rothwell
2011-12-06  3:16 ` Bjorn Helgaas
2011-12-06 17:28   ` Jesse Barnes
     [not found] <20110110125411.2f45fd2f.sfr@canb.auug.org.au>
2011-01-11 15:18 ` Narendra_K
2011-01-11 23:12   ` Stephen Rothwell
2010-10-18  2:20 Stephen Rothwell
2010-10-18  3:02 ` Jesse Barnes
2010-02-09  0:54 Stephen Rothwell
2010-02-09 16:27 ` 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=1319562878.2417.18.camel@zim.stowe \
    --to=mstowe@redhat.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=torvalds@linux-foundation.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).