All of lore.kernel.org
 help / color / mirror / Atom feed
From: jason@lakedaemon.net (Jason Cooper)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: mvebu: DT changes for v3.12
Date: Fri, 16 Aug 2013 09:00:47 -0400	[thread overview]
Message-ID: <20130816130047.GS13964@titan.lakedaemon.net> (raw)
In-Reply-To: <20130816063715.GI7035@quad.lixom.net>

On Thu, Aug 15, 2013 at 11:37:15PM -0700, Olof Johansson wrote:
> On Wed, Aug 14, 2013 at 04:16:30PM -0400, Jason Cooper wrote:
> > Arnd, Olof,
> > 
> > Here's the DT changes for v3.12 that didn't accompany driver conversions
> > (MBus, mv643xx_eth, clocksource, irqchip, msi/pci, etc).  I've attached
> > the conflict resolution below.  The small conflict in the binding
> > documentation is against arm-soc/for-next as well.  The rest is against
> > mvebu/boards.
> > 
> > Gregory CLEMENT (1):
> >       ARM: dts: mvebu: Introduce a new compatible string for mv64xxx-i2c
> 
> I didn't see any review of this patch by a device tree maintainer.
> 
> Also, there's a conflict with f480adaf1b7130ad43760f627b762f771fcfc5f5
> which is part of -rc5. That patch was merged through the i2c maintainer,
> so it would seem appropriate to do the same to this. Please get bindings
> acks or send the bindings update through a devicetree maintainer. dts/dtsi
> updates should still go through arm-soc. Given that the other update went in
> through the i2c maintainer, it could be appropriate to at least give him the
> choice of taking the bindings portion of this one as well.

You're right.  Gregory, I'm going to drop this one from mvebu/dt.
Please resubmit it as two patches (binding/dts changes) including the
devicetree mailinglist.

Olof, v2 of the pull (see, I didn't say 'PR' :) ) on it's way.

thx,

Jason.

  reply	other threads:[~2013-08-16 13:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-14 20:16 [GIT PULL] ARM: mvebu: DT changes for v3.12 Jason Cooper
2013-08-16  6:37 ` Olof Johansson
2013-08-16 13:00   ` Jason Cooper [this message]
2013-08-16 16:54 ` [GIT PULL v2] " Jason Cooper
2013-08-29 17:04   ` Olof Johansson

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=20130816130047.GS13964@titan.lakedaemon.net \
    --to=jason@lakedaemon.net \
    --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 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.