linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Giuseppe CAVALLARO <peppe.cavallaro@st.com>
To: Paul Mundt <lethal@linux-sh.org>
Cc: Chris Zankel <chris@zankel.net>,
	Linux-sh list <linux-sh@vger.kernel.org>,
	Linux MIPS Mailing List <linux-mips@linux-mips.org>,
	linux-kernel@vger.kernel.org,
	Linuxppc-dev <linuxppc-dev@ozlabs.org>,
	Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: Build regressions/improvements in v3.5-rc3
Date: Wed, 20 Jun 2012 14:50:07 +0200	[thread overview]
Message-ID: <4FE1C6FF.9070302@st.com> (raw)
In-Reply-To: <20120620035951.GC5623@linux-sh.org>

Hello Paul

On 6/20/2012 5:59 AM, Paul Mundt wrote:
> On Sun, Jun 17, 2012 at 09:56:59PM +0200, Geert Uytterhoeven wrote:
>> On Sun, Jun 17, 2012 at 9:46 PM, Geert Uytterhoeven
>> <geert@linux-m68k.org> wrote:
>>> JFYI, when comparing v3.5-rc3 to v3.5-rc2[3], the summaries are:
>>> ??- build errors: +235/-10
>>
>> Truckloads of powerpc "Unrecognized opcode" breakage, and
>>
> That was my fault, should be fixed up by 2603efa31a.
> 
>>   + drivers/net/ethernet/stmicro/stmmac/stmmac_pci.c: error: implicit
>> declaration of function 'pci_iomap'
>> [-Werror=implicit-function-declaration]:  => 90:3
>>   + drivers/net/ethernet/stmicro/stmmac/stmmac_pci.c: error: implicit
>> declaration of function 'pci_iounmap'
>> [-Werror=implicit-function-declaration]:  => 142:2
>>
> Not sure about this one, it should find everything alright via:
> 
> 	linux/io.h -> asm/io.h -> asm-generic/iomap.h -> asm-generic/pci_iomap.h
> 
> in the case that PCI is enabled. None of allyesconfig/modconfig enable
> PCI for me though, so I'm unsure of how you got in to this configuration
> to begin with?

Trying to reproduce the problem, I've also re-built the mainstream
kernel 3.5-rc3 for se7724_defconfig platform plus the stmmac (pltf and
pci) but all compiles fine.

I've also verified that there is the 33d5e332b9c5 commit that is the
latest one discussed/tested/committed in the network mailing list.

Can you tell me how to reproduce the problem? How can I help?

Pls let me know,
Peppe

  parent reply	other threads:[~2012-06-20 13:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1339962373-3224-1-git-send-email-geert@linux-m68k.org>
2012-06-17 19:56 ` Build regressions/improvements in v3.5-rc3 Geert Uytterhoeven
2012-06-17 21:53   ` Benjamin Herrenschmidt
2012-06-17 22:30     ` Andreas Schwab
2012-06-18 20:27   ` Kim Phillips
2012-06-18 20:35     ` Mauro Carvalho Chehab
2012-06-20  3:59   ` Paul Mundt
2012-06-20  8:02     ` Geert Uytterhoeven
2012-06-20 12:50     ` Giuseppe CAVALLARO [this message]
2012-06-20  6:27   ` [PATCH] MIPS: fix bug.h MIPS build regression Yoichi Yuasa
2012-06-20  7:09     ` John Crispin
2012-06-20 10:40     ` Sergei Shtylyov
2012-06-20 16:12     ` Ralf Baechle
2012-06-22 17:54       ` David Daney
2012-07-16 19:27         ` Geert Uytterhoeven
2012-07-18  8:35           ` Geert Uytterhoeven
2012-07-18 21:07             ` Andrew Morton

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=4FE1C6FF.9070302@st.com \
    --to=peppe.cavallaro@st.com \
    --cc=chris@zankel.net \
    --cc=geert@linux-m68k.org \
    --cc=lethal@linux-sh.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.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).