From: khilman@linaro.org (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: mvebu: driver changes for v3.13 (round 2)
Date: Thu, 17 Oct 2013 15:00:55 -0700 [thread overview]
Message-ID: <87wqlbzhew.fsf@linaro.org> (raw)
In-Reply-To: <20131017133944.GF22434@titan.lakedaemon.net> (Jason Cooper's message of "Thu, 17 Oct 2013 09:39:44 -0400")
Jason Cooper <jason@lakedaemon.net> writes:
> Guys,
>
> Here's the next round of driver changes for mvebu. As previously
> arranged with Bjorn, we're taking the pci-mvebu.c changes this time
> around since the previous pull request had pci changes depending on
> changes in irqchip.
Luckily, I remember you pointed us to the discussions where Bjorn agreed
with the approach in the first round, but my brain prefers forgetting
things to remembering them so in the future, please try and get his ack
on the drivers/pci changes so we don't have to rely on my memory to go
wading through the archives.
> The following changes since commit 96ae0b548672adc12431312718835e77472f5bf0:
>
> ARM: mvebu: fix gated clock documentation (2013-10-08 15:17:56 +0000)
>
> are available in the git repository at:
>
> git://git.infradead.org/linux-mvebu.git tags/drivers-3.13-2
>
> for you to fetch changes up to f5072dfbac053200c8865c4fb15e4f020b7b5d1d:
>
> PCI: mvebu: make local functions static (2013-10-08 17:57:40 +0000)
>
> ----------------------------------------------------------------
> mvebu driver changes for v3.13 (round 2)
>
> - mvebu
> - pcie
> - dynamic link up detection
> - add IO wrappers
> - declare some local functions static
>
> ----------------------------------------------------------------
Pulled into next/drivers.
Thanks,
Kevin
prev parent reply other threads:[~2013-10-17 22:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-17 13:39 [GIT PULL] ARM: mvebu: driver changes for v3.13 (round 2) Jason Cooper
2013-10-17 22:00 ` Kevin Hilman [this message]
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=87wqlbzhew.fsf@linaro.org \
--to=khilman@linaro.org \
--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).