From: shawn.guo@freescale.com (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: imx: SoC changes for 3.17
Date: Sun, 20 Jul 2014 10:08:01 +0800 [thread overview]
Message-ID: <20140720020800.GE8537@dragon> (raw)
In-Reply-To: <20140719191152.GD4265@quad.lixom.net>
On Sat, Jul 19, 2014 at 12:11:52PM -0700, Olof Johansson wrote:
> Nice diffstat. I would have liked to see the cleanups split off in a separate
> preceding branch (and the soc updates build on top if needed), so please keep
> that in mind in the future.
Okay, noted.
> The slightly bigger hassle is the defconfig update, since you touched
> multi_v7_defconfig: we tend to want to merge or apply that separately since
> they tend to cause a lot of conflicts between our branches.
Yes, I should have asked people to submit multi_v7_defconfig change
separately to you guys.
> Still, I'll give you a pass this time, it's a small change so we can manage it.
> Please separate more in the future though.
>
> Merged.
Thanks, Olof.
Shawn
prev parent reply other threads:[~2014-07-20 2:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-18 9:21 [GIT PULL] ARM: imx: SoC changes for 3.17 Shawn Guo
2014-07-19 19:11 ` Olof Johansson
2014-07-20 2:08 ` Shawn Guo [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=20140720020800.GE8537@dragon \
--to=shawn.guo@freescale.com \
--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).