From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL][for v3.17] pull request on fixing PXA DT
Date: Wed, 27 Aug 2014 15:03:10 -0700 [thread overview]
Message-ID: <20140827220310.GA13392@localhost> (raw)
In-Reply-To: <CAN1soZz_j2=DzazzLC1FV+kDtyhHRb4CYY3=vm+OmwEhQ1SqWA@mail.gmail.com>
On Mon, Aug 25, 2014 at 03:37:13PM +0800, Haojian Zhuang wrote:
> Hi Olof, Arnd, Kevin,
>
> Please help to merge the pull request from PXA git tree.
>
> Best Regards
> Haojian
>
> The following changes since commit 7d1311b93e58ed55f3a31cc8f94c4b8fe988a2b9:
>
> Linux 3.17-rc1 (2014-08-16 10:40:26 -0600)
>
> are available in the git repository at:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/hzhuang1/linux.git
> tags/fix-pxa-dt-v3.17
>
> for you to fetch changes up to 960a1042caf5e2f96fe9ddff98a4735aa9288080:
>
> ARM: pxa3xx: provide specific platform_devices for all ssp ports
> (2014-08-25 15:10:54 +0800)
>
> ----------------------------------------------------------------
> Fix DT bindings on PXA MMC/USB/SOUND
>
> ----------------------------------------------------------------
> Daniel Mack (4):
> ARM: pxa: dts: fix mmc controller compatible string
> ARM: pxa: dts: fix ohci controller compatible string
> ARM: pxa: ssp: provide platform_device_id for PXA3xx
> ARM: pxa3xx: provide specific platform_devices for all ssp ports
Hi,
I replied to one of the compatible string emails -- those should be done
for 3.18 and the driver regression needs to be fixed.
For the latter two fixes, what's not explained in the changelogs is what
is actually broken. How does this breakage affect a user? If it is a
regression, please also include what caused the breakage.
-Olof
prev parent reply other threads:[~2014-08-27 22:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-25 7:37 [GIT PULL][for v3.17] pull request on fixing PXA DT Haojian Zhuang
2014-08-27 22:03 ` Olof Johansson [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=20140827220310.GA13392@localhost \
--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 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).