linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Vitaly Bordug <vbordug@ru.mvista.com>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH 1/5] [POWERPC] cpm2: CPM2 interrupt controller fix
Date: Wed, 24 Jan 2007 16:05:44 +0300	[thread overview]
Message-ID: <20070124160544.4bad687c@localhost.localdomain> (raw)
In-Reply-To: <17847.12237.166954.453166@cargo.ozlabs.ibm.com>

[-- Attachment #1: Type: text/plain, Size: 1135 bytes --]

On Wed, 24 Jan 2007 21:07:09 +1100
Paul Mackerras wrote:

> I just tried to compile up the ads8272_defconfig with ARCH=ppc, since
> that was the only obviously 8272-based config in arch/ppc/configs.
> However, arch/ppc/platforms/mpc8272ads_setup.c fails to compile
> because of things like this in it (line 106):
That default config is just odd, as I have noticed while testing.
It still configured to use obsoleted stuff in 8260_io/ for network. 

Yet that does not address the problem below.

> 
> static void init_fcc1_ioports(struct fs_platform_info*)
> {
> ...
> }
> 
> That is, it's a function definition (not declaration) with the
> parameter name missing, which gcc rejects with an error.  Gitk tells
> me it's been like this since September.
> 
> Is there any 8272-based config that actually still compiles with
> ARCH=ppc?
>

No, there are not. 8272 haven't got a lot of attention in ppc realm. There are also some additional issues caused by say
PHY layer update, etc. The patch that fixes all is ready though - I'll give it a try today and send to the list later today.

--
Thanks, 
Vitaly 

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2007-01-24 13:05 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-13  0:41 [PATCH 1/5] [POWERPC] cpm2: CPM2 interrupt controller fix Vitaly Bordug
2007-01-13  0:42 ` [PATCH 2/5] [POWERPC] cpm_uart: OF-related fix for arch/powerpc Vitaly Bordug
2007-01-22 10:02   ` Paul Mackerras
2007-01-22 13:55     ` Vitaly Bordug
2007-01-13  0:42 ` [PATCH 3/5] [FS_ENET] OF-related fixup for FEC and SCC MAC's Vitaly Bordug
2007-01-22 10:07   ` Paul Mackerras
2007-01-22 14:04     ` Vitaly Bordug
2007-01-13  0:42 ` [PATCH 4/5] [POWERPC] Fix kernel build errors for mpc8272ads and mpc8560ads Vitaly Bordug
2007-01-13  0:42 ` [PATCH 5/5] [POWERPC] mpc8272ads: defconfig Vitaly Bordug
2007-01-22  9:57 ` [PATCH 1/5] [POWERPC] cpm2: CPM2 interrupt controller fix Paul Mackerras
2007-01-22 13:43   ` Vitaly Bordug
2007-01-22 19:55     ` Benjamin Herrenschmidt
2007-01-22 20:55       ` Vitaly Bordug
2007-01-22 21:13         ` Benjamin Herrenschmidt
2007-01-22 21:42           ` Vitaly Bordug
2007-01-24 10:07             ` Paul Mackerras
2007-01-24 13:05               ` Vitaly Bordug [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=20070124160544.4bad687c@localhost.localdomain \
    --to=vbordug@ru.mvista.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.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).