linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: sparclinux@vger.kernel.org, ppc-dev <linuxppc-dev@ozlabs.org>,
	paulus@samba.org, "David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH 08/11] Begin to consolidate of_device.c
Date: Wed, 2 May 2007 03:23:19 +0200	[thread overview]
Message-ID: <5e7183d982a071c0e9dc7c7843caf6e7@kernel.crashing.org> (raw)
In-Reply-To: <20070501173143.9d514ea4.sfr@canb.auug.org.au>

> This moves all the common parts for the Sparc, Sparc64 and PowerPC
> of_device.c files into drivers/openfw/device.c.

s/openfw/of/

Cheers,


Segher

  reply	other threads:[~2007-05-02  1:23 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-01  7:22 [PATCH 0/11] Consolidation of Open Firmware routines Stephen Rothwell
2007-05-01  7:24 ` [PATCH 01/11] Split out common parts of prom.h Stephen Rothwell
2007-05-01  7:25 ` [PATCH 02/11] Start split out of common open firmware code Stephen Rothwell
2007-05-01  7:26 ` [PATCH 03/11] Consolidate of_device_is_compatible Stephen Rothwell
2007-05-01  7:27 ` [PATCH 04/11] Consolidate of_find_property Stephen Rothwell
2007-05-01  7:28 ` [PATCH 05/11] Consolidate of_get_parent Stephen Rothwell
2007-05-01  7:29 ` [PATCH 06/11] Consolidate of_get_next_child Stephen Rothwell
2007-05-01  7:30 ` [PATCH 07/11] Consolidate of_find_node_by routines Stephen Rothwell
2007-05-01  7:31 ` [PATCH 08/11] Begin to consolidate of_device.c Stephen Rothwell
2007-05-02  1:23   ` Segher Boessenkool [this message]
2007-05-01  7:32 ` [PATCH 09/11] Begin consolidation of of_device.h Stephen Rothwell
2007-05-01  7:33 ` [PATCH 10/11] [SPARC/64] Rename some functions like PowerPC Stephen Rothwell
2007-05-01  7:34 ` [PATCH 11/11] Create linux/of_platorm.h Stephen Rothwell
2007-05-01  8:30 ` [PATCH 0/11] Consolidation of Open Firmware routines Jan Engelhardt
2007-05-01  8:51   ` David Miller
2007-05-01 11:17     ` Jan Engelhardt
2007-05-01 19:36       ` David Miller

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=5e7183d982a071c0e9dc7c7843caf6e7@kernel.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=davem@davemloft.net \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.org \
    --cc=sfr@canb.auug.org.au \
    --cc=sparclinux@vger.kernel.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).