linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 for 3.10] Introduce a Marvell EBU MBus driver
Date: Mon, 18 Mar 2013 14:59:10 +0000	[thread overview]
Message-ID: <201303181459.10954.arnd@arndb.de> (raw)
In-Reply-To: <51422AD5.9020203@free-electrons.com>

On Thursday 14 March 2013, Gregory CLEMENT wrote:
> Will you agree to take this patch set as is ?(modulo some fixes needed
> for the not yet tested platforms).
> 
> This patch set is a great step in the right way to move code outside
> arch/arm. I know that Arnd would like a greater step and a more
> radical approach to have a more accurate device tree bindings.
> However the purpose of this patch set was initially to ease the merge
> of the PCIe support not to delay it! And I fear that the large number
> of files to change and the resulting conflicts will prevent this patch
> set to be merged in a single release.
> 
> I agree that the bindings could be improve but can we consider this
> patch set as a first step ?

I would prefer not to merge the DT binding, but I'm fine with the
current implementation, as in the pull request that Jason sent
me. How about this:

* You remove the Documentation/devicetree/bindings/arm/mvebu-mbus.txt file
  that is the main source of disagreement, along with the mvebu_mbus_dt_init
  function.
* All conversion patches get changed to not add properties to the soc
  node but instead call mvebu_mbus_init directly. That code is there
  already.

I can take those patches, and we can work on a better DT binding for
a later release without having to hold up other conversions.

	Arnd

  reply	other threads:[~2013-03-18 14:59 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-06 16:59 [PATCH v2 for 3.10] Introduce a Marvell EBU MBus driver Thomas Petazzoni
2013-03-06 16:59 ` [PATCH 01/10] arm: plat-orion: only build addr-map.c when needed Thomas Petazzoni
2013-03-06 16:59 ` [PATCH 02/10] arm: plat-orion: use mv_mbus_dram_info() in PCIe code Thomas Petazzoni
2013-03-06 16:59 ` [PATCH 03/10] arm: mach-orion5x: use mv_mbus_dram_info() in PCI code Thomas Petazzoni
2013-03-06 16:59 ` [PATCH 04/10] bus: introduce an Marvell EBU MBus driver Thomas Petazzoni
2013-03-06 17:00 ` [PATCH 05/10] arm: mach-mvebu: convert to use mvebu-mbus driver Thomas Petazzoni
2013-03-06 17:00 ` [PATCH 06/10] arm: mach-kirkwood: " Thomas Petazzoni
2013-03-06 17:00 ` [PATCH 07/10] arm: mach-dove: " Thomas Petazzoni
2013-03-06 17:00 ` [PATCH 08/10] arm: mach-orion5x: " Thomas Petazzoni
2013-03-06 17:00 ` [PATCH 09/10] arm: mach-mv78xx0: convert to use the " Thomas Petazzoni
2013-03-06 17:00 ` [PATCH 10/10] arm: plat-orion: remove addr-map code Thomas Petazzoni
2013-03-14 19:53 ` [PATCH v2 for 3.10] Introduce a Marvell EBU MBus driver Gregory CLEMENT
2013-03-18 14:59   ` Arnd Bergmann [this message]
2013-03-18 15:24     ` Thomas Petazzoni
2013-03-18 15:58       ` Arnd Bergmann
2013-03-18 16:26         ` Jason Cooper
2013-03-17 18:59 ` Jason Cooper

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=201303181459.10954.arnd@arndb.de \
    --to=arnd@arndb.de \
    --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).