linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: michael@walle.cc (Michael Walle)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] [orion] move *_mbus_dram_info out of platform_data
Date: Tue, 6 Dec 2011 19:57:40 +0100	[thread overview]
Message-ID: <201112061957.40740.michael@walle.cc> (raw)
In-Reply-To: <1321599572-705-1-git-send-email-andrew@lunn.ch>

Hi,

> As a step towords device tree support for orion based system, this
> patchset removes the *_mbus_dram_info from platform_data for various
> devices and replaces it with one instance of the strucutre in
> plat-orion and a getter function to retreive it. In order that
> none orion usage of these drivers still work, a dummy function is
> also provided which returns NULL, indicating it is not necassary
> to perform address map setup.
> 
> Boot tested on kirkwood, compile tested on other orion based systems.

For all four patches:

Tested-By: Michael Walle <michael@walle.cc>

-- 
Michael

  parent reply	other threads:[~2011-12-06 18:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-18  6:59 [PATCH 0/4] [orion] move *_mbus_dram_info out of platform_data Andrew Lunn
2011-11-18  6:59 ` [PATCH 1/4] [orion] Consolidate the address map setup on Orion based platforms Andrew Lunn
2011-11-18  6:59 ` [PATCH 2/4] [orion] Move the *_mbus_dram_info structure into the orion platform and call it orion_mbus_dram_info everywhere Andrew Lunn
2011-11-18  6:59 ` [PATCH 3/4] [orion] Get address map from plat-orion instead of via platform_data Andrew Lunn
2011-11-18  6:59 ` [PATCH 4/4] [orion] Remove address map info from all platform data strucutures Andrew Lunn
2011-12-06 18:57 ` Michael Walle [this message]
2011-12-15 16:10 ` [PATCH 0/4] [orion] move *_mbus_dram_info out of platform_data Jason

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=201112061957.40740.michael@walle.cc \
    --to=michael@walle.cc \
    --cc=linux-arm-kernel@lists.infradead.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).