public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robherring2@gmail.com>
To: Olof Johansson <olof@lixom.net>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	arm@kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL 0/5] Second batch of arm-soc changes
Date: Wed, 28 Mar 2012 09:26:50 -0500	[thread overview]
Message-ID: <4F731FAA.5040708@gmail.com> (raw)
In-Reply-To: <1332918842-13521-1-git-send-email-olof@lixom.net>

On 03/28/2012 02:13 AM, Olof Johansson wrote:
> Hi Linus,
> 
> Here is the second batch of arm-soc changes for this merge window. As Arnd
> mentioned with the first cover letter, most of these either had external
> dependencies that have now been pulled in, or just needed a bit more
> linux-next bake time due to getting picked up close to the 3.3 release.
> 
> 
> There are 128 non-merge patches, with a total diffstat of:
> 
>  346 files changed, 10790 insertions(+), 2792 deletions(-)
> 
> So, while there's been some good cleanups especially in the first branch,
> there's been a net addition of code:
> 
> * New SoC family support for Samsung EXYNOS5250: clock tables, driver
>   updates, etc means net gain in code.
> * Added device tree conversions. Once we start to sunset non-device tree
>   boards on the enabled platforms, we should see payback in code removal.
> * Common clock framework. As SoCs get converted over to the framework,
>   we should see more code removal from this as well.
> 
> 
> There are a handful of merge conflicts on the branches, nothing that
> should be too messy to sort out. I've described each conflict in the
> corresponding pull request, including how we've resolved them in our
> for-next branch.
> 

Why isn't lakml getting copied on emails 1-5? The same thing happened
with Arnd's pull request. Are they getting hung up for moderator approval?

Rob

  parent reply	other threads:[~2012-03-28 14:26 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-28  7:13 [GIT PULL 0/5] Second batch of arm-soc changes Olof Johansson
2012-03-28  7:13 ` [GIT PULL 1/5] ARM: cleanups of io includes Olof Johansson
2012-03-28  8:25   ` Russell King - ARM Linux
2012-03-28  9:05     ` Olof Johansson
2012-03-28 12:34       ` Arnd Bergmann
2012-03-28 19:28       ` Russell King - ARM Linux
2012-03-30  0:09         ` Linus Torvalds
2012-03-30  0:27           ` Olof Johansson
2012-03-30  0:34             ` Olof Johansson
2012-03-28  7:13 ` [GIT PULL 2/5] ARM: More SoC driver updates Olof Johansson
2012-03-28  7:14 ` [GIT PULL 3/5] ARM: More SoC support updates Olof Johansson
2012-03-28  7:14 ` [GIT PULL 4/5] ARM: More device tree " Olof Johansson
2012-03-28 19:36   ` Linus Torvalds
2012-03-28 20:58     ` Arnd Bergmann
2012-03-28  7:14 ` [GIT PULL 5/5] drivers/clk: common clock framework Olof Johansson
2012-03-28 14:26 ` Rob Herring [this message]
2012-03-28 14:59   ` [GIT PULL 0/5] Second batch of arm-soc changes Arnd Bergmann

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=4F731FAA.5040708@gmail.com \
    --to=robherring2@gmail.com \
    --cc=arm@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olof@lixom.net \
    --cc=torvalds@linux-foundation.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