From: Stephen Boyd <sboyd@codeaurora.org>
To: Arnd Bergmann <arnd@arndb.de>, linux-arm-kernel@lists.infradead.org
Cc: arm@kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org, Rob Clark <robdclark@gmail.com>,
Dave Airlie <airlied@redhat.com>,
David Brown <davidb@codeaurora.org>, Chris Ball <cjb@laptop.org>
Subject: Re: [PATCH v2 0/7] Allow MSM DT platforms to be built multi-platform
Date: Fri, 03 Jan 2014 10:51:04 -0800 [thread overview]
Message-ID: <52C70698.2030004@codeaurora.org> (raw)
In-Reply-To: <201401021913.25920.arnd@arndb.de>
On 01/02/14 10:13, Arnd Bergmann wrote:
> On Monday 30 December 2013, Stephen Boyd wrote:
>> These patches allow the DT based MSM platforms to be built as part of the
>> multi-platform kernel. I need acks from Chris Ball on the mmc patch and
>> Rob/Dave on the drm patch. I dropped Arnd's ack on patch 6 because I've
>> rebased that patch on top of the patchset David sent out (which this is in
>> reply to). The rebase was fairly minor and the new patch for drm/msm is
>> trivial. Please consider for v3.14.
> Just for the record, I'm definitely happy with the way this is turning out,
> don't see my question on the serial driver as a NAK. I assume we will apply
> the patches for 3.14, but I first want to have a better understanding on
> where we are with the stuff that is already queued up for 3.14.
>
It would be great if we could get these patches in for 3.14. Now that
Olof has applied the collection of patches that David sent, these
patches should apply cleanly on top of arm-soc.git qcom/soc. Can you
apply them directly to the arm-soc tree?
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
next prev parent reply other threads:[~2014-01-03 18:51 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-30 21:15 [PATCH v2 0/7] Allow MSM DT platforms to be built multi-platform Stephen Boyd
2013-12-30 21:15 ` [PATCH v2 1/7] usb: phy: msm: Move mach dependent code to platform data Stephen Boyd
2013-12-30 21:15 ` [PATCH v2 2/7] mmc: msm_sdcc: Limit driver to platforms that use it Stephen Boyd
2013-12-30 21:15 ` [PATCH v2 3/7] tty: serial: Limit msm_serial_hs " Stephen Boyd
2014-01-02 18:10 ` Arnd Bergmann
2014-01-02 20:20 ` Stephen Boyd
2014-01-02 20:26 ` Arnd Bergmann
2013-12-30 21:15 ` [PATCH v2 4/7] ARM: msm: Only build clock.c on proc_comm based platforms Stephen Boyd
2013-12-30 21:15 ` [PATCH v2 5/7] ARM: msm: Only build timer.c if required Stephen Boyd
2013-12-30 21:15 ` [PATCH v2 6/7] drm/msm: Drop unnecessary mach include Stephen Boyd
2013-12-30 21:20 ` Stephen Boyd
2013-12-31 1:12 ` Rob Clark
2013-12-31 1:19 ` Rob Clark
2013-12-31 5:15 ` Stephen Boyd
2014-01-09 8:13 ` Olof Johansson
2014-01-09 18:40 ` Stephen Boyd
2013-12-30 21:15 ` [PATCH v2 7/7] ARM: msm: Move MSM's DT based hardware to multi-platform support Stephen Boyd
2013-12-30 21:17 ` [PATCH v2 0/7] Allow MSM DT platforms to be built multi-platform Stephen Boyd
2014-01-02 18:13 ` Arnd Bergmann
2014-01-03 18:51 ` Stephen Boyd [this message]
2014-01-03 19:31 ` Olof Johansson
2014-01-09 8:11 ` 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=52C70698.2030004@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=airlied@redhat.com \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=cjb@laptop.org \
--cc=davidb@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robdclark@gmail.com \
/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).