All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olof Johansson <olof@lixom.net>
To: David Brown <davidb@codeaurora.org>
Cc: arm@kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-msm@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/7] MSM patches for 3.14
Date: Thu, 2 Jan 2014 10:31:00 -0800	[thread overview]
Message-ID: <20140102183100.GA8684@quad.lixom.net> (raw)
In-Reply-To: <1387566560-23948-1-git-send-email-davidb@codeaurora.org>

On Fri, Dec 20, 2013 at 11:09:13AM -0800, David Brown wrote:
> The following series contains a warning fix, a bit of cleanup, adds a
> few more boards.  There are still numerous patches floating with
> issues, but things seem to be moving in the right direction.
> 
> These have all been sent previously to the lists, and received reviews
> and necessary acks.
> 

Hi,

I've applied these across the various branches, i.e I split the series up
into fixes, soc, dt and board changes.

I chose to split the Dragonboard patch up into two patches instead of one:
One that adds SoC support, and a second that adds the board support. I
rephrased commit messages accordingly but the contents was untouched
(just split up).

I hope the clock stuff can be sorted out real quick so we get working support
for more useful IP on the SoC in time for 3.14.


-Olof

WARNING: multiple messages have this Message-ID (diff)
From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/7] MSM patches for 3.14
Date: Thu, 2 Jan 2014 10:31:00 -0800	[thread overview]
Message-ID: <20140102183100.GA8684@quad.lixom.net> (raw)
In-Reply-To: <1387566560-23948-1-git-send-email-davidb@codeaurora.org>

On Fri, Dec 20, 2013 at 11:09:13AM -0800, David Brown wrote:
> The following series contains a warning fix, a bit of cleanup, adds a
> few more boards.  There are still numerous patches floating with
> issues, but things seem to be moving in the right direction.
> 
> These have all been sent previously to the lists, and received reviews
> and necessary acks.
> 

Hi,

I've applied these across the various branches, i.e I split the series up
into fixes, soc, dt and board changes.

I chose to split the Dragonboard patch up into two patches instead of one:
One that adds SoC support, and a second that adds the board support. I
rephrased commit messages accordingly but the contents was untouched
(just split up).

I hope the clock stuff can be sorted out real quick so we get working support
for more useful IP on the SoC in time for 3.14.


-Olof

  parent reply	other threads:[~2014-01-02 18:33 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-20 19:09 [PATCH 0/7] MSM patches for 3.14 David Brown
2013-12-20 19:09 ` David Brown
2013-12-20 19:09 ` [PATCH 1/7] ARM: msm: trout: fix uninit var warning David Brown
2013-12-20 19:09   ` David Brown
2013-12-20 19:09 ` [PATCH 2/7] ARM: msm: Add support for APQ8074 Dragonboard David Brown
2013-12-20 19:09   ` David Brown
2013-12-20 20:34   ` Arnd Bergmann
2013-12-20 20:34     ` Arnd Bergmann
2013-12-21  6:21     ` Stephen Boyd
2013-12-21  6:21       ` Stephen Boyd
2013-12-20 19:09 ` [PATCH 3/7] defconfig: msm_defconfig: Enable CONFIG_ARCH_MSM8974 David Brown
2013-12-20 19:09   ` David Brown
2013-12-20 19:09   ` David Brown
2013-12-20 19:09 ` [PATCH 4/7] ARM: msm: Simplify ARCH_MSM_DT config David Brown
2013-12-20 19:09   ` David Brown
2013-12-20 19:09 ` [PATCH 5/7] ARM: dts: MSM8974: Add restart node David Brown
2013-12-20 19:09   ` David Brown
2013-12-20 19:09 ` [PATCH 6/7] ARM: dts: MSM8974: Add MMIO architected timer node David Brown
2013-12-20 19:09   ` David Brown
2013-12-20 19:09 ` [PATCH 7/7] ARM: msm_defconfig: Enable restart driver David Brown
2013-12-20 19:09   ` David Brown
2014-01-02 18:31 ` Olof Johansson [this message]
2014-01-02 18:31   ` [PATCH 0/7] MSM patches for 3.14 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=20140102183100.GA8684@quad.lixom.net \
    --to=olof@lixom.net \
    --cc=arm@kernel.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 \
    /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.