All of lore.kernel.org
 help / color / mirror / Atom feed
From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL V2 2/4] ARM: mvebu: drivers for v3.9
Date: Sun, 27 Jan 2013 21:53:04 -0800	[thread overview]
Message-ID: <20130128055304.GA25723@quad.lixom.net> (raw)
In-Reply-To: <1358909285.ca5b742.21555@triton>

On Wed, Jan 23, 2013 at 02:48:05AM +0000, Jason Cooper wrote:
> The following changes since commit 4b53ab9cb853e446f628e561ce6fcc527df30a76:
> 
>   Merge branch 'mvebu/fixes' into mvebu/drivers (2013-01-23 01:42:14 +0000)
> 
> are available in the git repository at:
> 
> 
>   git://git.infradead.org/users/jcooper/linux.git tags/drivers_for_v3.9
> 
> for you to fetch changes up to 43076a4c4e5fb92721bedc5d05b93468d6d76b2c:
> 
>   mmc: mvsdio: add pinctrl integration (2013-01-23 01:42:29 +0000)
> 
> ----------------------------------------------------------------
> mvebu drivers for v3.9
>  - mvsdio
>    - use slot-gpio for card detect and write protect
>    - add DT binding
>    - add pinctrl integration
>  - use rtc-mv in mvebu armv7 SoCs
>  - add pci-e hotplug for kirkwood

Hi,

I didn't see any acks by Chris Ball on these, he's usually pretty
responsive on code reviews so I just wanted to make sure he's OK with
us taking this through arm-soc, and aware of it.

Looks like this whole branch could go through the mmc tree? The dtsi
updates from the last branch would still go through arm-soc.

Either way is fine with me, I just don't want to make life difficult for Chris
in case he has some sweeping changes planned that might cause conflicts, etc.


-Olof

  reply	other threads:[~2013-01-28  5:53 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-12 23:29 [GIT PULL 0/4] ARM: mvebu: changes for v3.9 Jason Cooper
2013-01-12 23:29 ` [GIT PULL 1/4] ARM: mvebu: cleanup " Jason Cooper
2013-01-12 23:29 ` [GIT PULL 2/4] ARM: mvebu: drivers " Jason Cooper
2013-01-12 23:29 ` [GIT PULL 3/4] ARM: mvebu: boards " Jason Cooper
2013-01-12 23:29 ` [GIT PULL 4/4] ARM: mvebu: dt " Jason Cooper
     [not found] ` <E1TuAWu-0004Jx-Hn@merlin.infradead.org>
2013-01-13  1:05   ` [GIT PULL 2/4] ARM: mvebu: drivers " Russell King - ARM Linux
2013-01-13  1:28     ` Jason Cooper
     [not found] ` <E1TuAWD-0004Ec-1G@merlin.infradead.org>
2013-01-13  1:06   ` [GIT PULL 3/4] ARM: mvebu: boards " Russell King - ARM Linux
     [not found] ` <E1TuAWi-0004H4-K6@merlin.infradead.org>
2013-01-13  1:06   ` [GIT PULL 4/4] ARM: mvebu: dt " Russell King - ARM Linux
2013-01-13  1:30     ` Jason Cooper
2013-01-23  2:48 ` [GIT PULL V2 0/4] ARM: mvebu: changes " Jason Cooper
2013-01-23  2:48   ` [GIT PULL V2 1/4] ARM: mvebu: cleanup " Jason Cooper
2013-01-28  5:57     ` Olof Johansson
2013-01-23  2:48   ` [GIT PULL V2 2/4] ARM: mvebu: drivers " Jason Cooper
2013-01-28  5:53     ` Olof Johansson [this message]
2013-01-28 11:53       ` Chris Ball
2013-01-28 16:10         ` Jason Cooper
2013-01-23  2:48   ` [GIT PULL V2 3/4] ARM: mvebu: boards " Jason Cooper
2013-01-23  2:48   ` [GIT PULL V2 4/4] ARM: mvebu: dt " 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=20130128055304.GA25723@quad.lixom.net \
    --to=olof@lixom.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.