All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Olaf Hering <olh@suse.de>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH] powerpc: Remove device_node addrs/n_addr
Date: Tue, 03 Jan 2006 09:01:35 +1100	[thread overview]
Message-ID: <1136239296.24205.18.camel@localhost.localdomain> (raw)
In-Reply-To: <20060102131539.GA12434@suse.de>

On Mon, 2006-01-02 at 14:15 +0100, Olaf Hering wrote:
>  On Tue, Dec 13, Benjamin Herrenschmidt wrote:
> 
> > The pre-parsed addrs/n_addrs fields in struct device_node are finally
> > gone. Remove the dodgy heuristics that did that parsing at boot and
> > remove the fields themselves since we now have a good replacement with
> > the new OF parsing code. This patch also fixes a bunch of drivers to use
> > the new code instead, so that at least pmac32, pseries, iseries and g5
> > defconfigs build.
> 
> > +++ linux-work/include/asm-powerpc/prom.h	2005-12-13 17:51:20.000000000 +1100
> 
> > @@ -120,8 +82,6 @@ struct device_node {
> >  	char	*type;
> >  	phandle	node;
> >  	phandle linux_phandle;
> > -	int	n_addrs;
> > -	struct	address_range *addrs;
> >  	int	n_intrs;
> >  	struct	interrupt_info *intrs;
> >  	char	*full_name;
> 
> Is this patch supposed to be complete? I will find references to n_addrs
> in arch/powerpc:
> 
> hydra_init, chrp_find_bridges, chrp_find_openpic, comment in
> of_finish_dynamic_node.

No, it's complete as far as powermac is concerned. I'll deal with the
remaining bits this week.

Ben.

      reply	other threads:[~2006-01-02 22:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-13  7:01 [PATCH] powerpc: Remove device_node addrs/n_addr Benjamin Herrenschmidt
2006-01-02 13:15 ` Olaf Hering
2006-01-02 22:01   ` Benjamin Herrenschmidt [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=1136239296.24205.18.camel@localhost.localdomain \
    --to=benh@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=olh@suse.de \
    /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.