From: Jon Loeliger <jdl@jdl.com>
To: "linuxppc-dev@ozlabs.org list" <linuxppc-dev@ozlabs.org>
Subject: Re: 8641 open nits
Date: Fri, 23 Jun 2006 10:31:13 -0500 [thread overview]
Message-ID: <E1Ftncn-0008Kb-PT@jdl.com> (raw)
In-Reply-To: Your message of "Fri, 23 Jun 2006 10:11:39 CDT." <6C66805F-22DD-4EC2-B852-101BF1E84612@kernel.crashing.org>
So, like, the other day Kumar Gala mumbled:
> Jon,
>
> Any update on the following nits:
> * duplication of entry in cputable
Earlier, we discussed it internally, and there are a few
issues differentiating the cores, so the sentiment was to
leave it as is for now.
> * include of <platforms/86xx/mpc8641_hpcn.h> in asm-powerpc/mpc86xx.h
That has to stay unless the IRQ patch is applied first.
Ben said "No" to that one so far. The include stays for now.
> * mpc86xx_exclude_device cleanup and movement to pci.c
> * fixing up mpc86xx_hpcn_probe()
Those are all going to be cleaned up pending Ben's IRQ rewrite.
Thanks,
jdl
next prev parent reply other threads:[~2006-06-23 15:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-17 22:52 [PATCH 7/9 v3] Add 8641 Register space and IRQ definitions Jon Loeliger
2006-06-18 14:31 ` Kumar Gala
2006-06-23 15:11 ` 8641 open nits Kumar Gala
2006-06-23 15:31 ` Jon Loeliger [this message]
2006-06-23 18:12 ` Kumar Gala
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=E1Ftncn-0008Kb-PT@jdl.com \
--to=jdl@jdl.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.