From: cjb@laptop•org (Chris Ball)
To: linux-arm-kernel@lists•infradead.org
Subject: [GIT PULL] mxs device tree support for v3.5
Date: Sat, 12 May 2012 20:41:22 -0400 [thread overview]
Message-ID: <87txzkzzd9.fsf@laptop.org> (raw)
In-Reply-To: <20120513001505.GK17875@S2101-09.ap.freescale.net> (Shawn Guo's message of "Sun, 13 May 2012 08:15:07 +0800")
Hi,
On Sat, May 12 2012, Shawn Guo wrote:
> On Sat, May 12, 2012 at 10:55:49AM -0400, Chris Ball wrote:
>> Hi Shawn,
>>
>> On Sat, May 12 2012, Shawn Guo wrote:
>> > Copy Chris in case he has problem with having mxs-mmc DT series go
>> > through arm-soc tree.
>>
>> Thanks, that's okay with me.
>>
>> I just sent out a small review comment on one of the MMC patches; once
>> that's changed, feel free to add for the series:
>>
>> Acked-by: Chris Ball <cjb@laptop•org>
>>
> Typo fixed, tag collected, branch updated. Thanks, Chris.
Thanks, branch looks good to me now.
>> I notice that Marek Vasut also gave you an Acked-by for the series,
>> but the version of the patches in your git tree doesn't show it.
>> Please make sure to credit people who review your patches by adding
>> their tags into patches before the patches are merged, it's important.
>>
> Hmm, I collected Marek's tag he put on patch #1, #4, #5, #6 #7.
Oops, I'm sorry for the false criticism -- I must have been looking at
one of the patches that Marek didn't ACK.
- Chris.
--
Chris Ball <cjb@laptop•org> <http://printf.net/>
One Laptop Per Child
next prev parent reply other threads:[~2012-05-13 0:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-12 8:20 [GIT PULL] mxs device tree support for v3.5 Shawn Guo
2012-05-12 11:27 ` Shawn Guo
2012-05-12 14:55 ` Chris Ball
2012-05-13 0:15 ` Shawn Guo
2012-05-13 0:41 ` Chris Ball [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-04-05 1:36 [GIT PULL] mxs: " Shawn Guo
2012-04-15 18:29 ` Olof Johansson
2012-05-07 13:54 ` Shawn Guo
2012-05-10 7:17 ` Olof Johansson
2012-05-10 7:55 ` Shawn Guo
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=87txzkzzd9.fsf@laptop.org \
--to=cjb@laptop$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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