From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: mvebu: driver changes for v3.13
Date: Mon, 7 Oct 2013 10:02:06 -0700 [thread overview]
Message-ID: <20131007170206.GE15413@quad.lixom.net> (raw)
In-Reply-To: <20130930153643.GF31178@titan.lakedaemon.net>
Hi Jason,
On Mon, Sep 30, 2013 at 11:36:43AM -0400, Jason Cooper wrote:
> Guys,
>
> Here are all of the driver changes that didn't make it during the last
> merge window. They've been in -next since v3.12-rc1, without
> merge-conflicts or build issues.
It looks like the PCI pieces here are all independent now and can go through
Bjorn's tree instead of arm-soc. Or do you anticipate having something
dependent on this later on such that we should take it?
For 3.12 it was easier to take through arm-soc since this built on top of the
other PCI/MSI work we were queueing.
If you want us to take it, see if you can shake an ack out of Bjorn, mostly to
make sure he's aware that there's PCI code going through our tree.
-Olof
next prev parent reply other threads:[~2013-10-07 17:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-30 15:36 [GIT PULL] ARM: mvebu: driver changes for v3.13 Jason Cooper
2013-10-07 17:02 ` Olof Johansson [this message]
2013-10-07 18:04 ` Jason Cooper
2013-10-08 15:49 ` [GIT PULL V2] " Jason Cooper
2013-10-09 20:20 ` Kevin Hilman
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=20131007170206.GE15413@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.