linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dale Farnsworth <dale@farnsworth.org>
To: paulus@samba.org
Cc: linuxppc-dev@ozlabs.org
Subject: [PATCH 0/8 v3] [POWERPC] mv64x60 and prpmc2800 DTS cleanups
Date: Mon, 7 Apr 2008 15:00:27 -0700	[thread overview]
Message-ID: <20080407220027.GA24510@farnsworth.org> (raw)

This series of patches again attempts to clean up and document
the Marvell MV64x60 device tree.  It supersedes Mark Greer's
series posted on 11 December 2007.  See:
http://ozlabs.org/pipermail/linuxppc-dev/2007-December/047986.html

These apply on the powerpc-next branch, and I'd like to get them
into 2.6.26.

This series differs from v2 in that the compatible property
prefix string has been left unchanged as "marvell".

Thanks,
-Dale

             reply	other threads:[~2008-04-07 22:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-07 22:00 Dale Farnsworth [this message]
2008-04-07 22:07 ` [PATCH 1/8 v3] [POWERPC] prpmc2800: convert DTS to v1 and add labels Dale Farnsworth
2008-04-07 22:08 ` [PATCH 2/8 v3] [POWERPC] prpmc2800: fix frequencies in prpmc2800.dts Dale Farnsworth
2008-04-07 22:09 ` [PATCH 3/8 v3] [POWERPC] mv64x60: Fix FDT compatible names: mv64x60 => mv64360 Dale Farnsworth
2008-04-07 22:09 ` [PATCH 4/8 v3] [POWERPC] mv64x60: remove device tree absolute path references Dale Farnsworth
2008-04-07 22:10 ` [PATCH 5/8 v3] [POWERPC] prpmc2800: clean up dts properties Dale Farnsworth
2008-04-07 22:11 ` [PATCH 6/8 v3] [POWERPC] mv643xx_eth: prepare to support multiple silicon blocks Dale Farnsworth
2008-04-07 22:12 ` [PATCH 7/8 v3] [POWERPC] Document the mv64x60 device tree bindings Dale Farnsworth
2008-04-07 22:13 ` [PATCH 8/8 v3] [POWERPC] prpmc2800 needs a dtbImage Dale Farnsworth

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=20080407220027.GA24510@farnsworth.org \
    --to=dale@farnsworth.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).