linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Vitaly Bordug <vbordug@ru.mvista.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev <linuxppc-dev@ozlabs.org>,
	Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH 1/5] [POWERPC] cpm2: CPM2 interrupt controller fix
Date: Tue, 23 Jan 2007 00:42:03 +0300	[thread overview]
Message-ID: <20070123004203.5a3007fa@localhost.localdomain> (raw)
In-Reply-To: <1169500388.1582.14.camel@localhost.localdomain>

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

On Tue, 23 Jan 2007 08:13:08 +1100
Benjamin Herrenschmidt wrote:

> 
> > Compilation fails on locating various CPM-related defines, that
> > used to be in ppc/io.h. So, not to mangle new io.h I've added
> > mpc8260.h to have them defined there. This is not that beautiful,
> > but stuff that is claimed to be supported should work and at least
> > not bail out the compiler :).
> > 
> > I have appropriate fix in the queue, that gets rid of global IMMAP
> > pointer yet keeping ppc happy, but the patch is to significant to
> > get into the current kernel.
> 
> What about an fsl_cpm.h instead if that CPM exists on more than just
> 8260 ? (If not, that's ok then)

Because other than cpm-related that are common, it has some
board-specific defines,
that are accomplished old-way by

+#if defined(CONFIG_PQ2ADS) || defined (CONFIG_PQ2FADS) 
+#include <platforms/82xx/pq2ads.h>
+#endif                                                

That was pointed out by Kumar already, but he agreed that proper approach is much more significant to 
be considered as bugfix.

After my forthcoming CPM cleanup series we'll be able to get rid of this header... Well, most of it at least, I need to 
double-check. Anyway, this approach is the closest to what have been hit by the io.h removal (just peek into ppc/ version :) )	

Thanks
--
Sincerely, Vitaly

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

  reply	other threads:[~2007-01-22 22:53 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 [this message]
2007-01-24 10:07             ` Paul Mackerras
2007-01-24 13:05               ` Vitaly Bordug

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=20070123004203.5a3007fa@localhost.localdomain \
    --to=vbordug@ru.mvista.com \
    --cc=benh@kernel.crashing.org \
    --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).