From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 3/3] ARM: mvebu: soc for v3.10
Date: Mon, 18 Mar 2013 17:18:24 +0100 [thread overview]
Message-ID: <20130318171824.44814271@skate> (raw)
In-Reply-To: <20130318010726.GF13280@titan.lakedaemon.net>
Dear Jason Cooper,
On Sun, 17 Mar 2013 21:07:26 -0400, Jason Cooper wrote:
> On Sun, Mar 17, 2013 at 11:26:10PM +0100, Gregory CLEMENT wrote:
> > I managed to test Thomas patch set for a mv78x00 based board on Friday,
> > and I found a small bug. Thomas has a fix for it and he plans to send
> > a V3 with this fix next week.
>
> A reply to the V2 patch would have been appreciated. The series has
> been on lakml since Mar 6th, with no comments...
Gregory managed to test the series on Friday, 15th March, and I did a
quick fix on that day. I've been on WE on Saturday/Sunday, so please
excuse the delay.
> Please just send a new version of the mv78xx0 patch. No need for a new
> series.
Seeing the discussion with Arnd, it seems like a new series will be
needed. Not because of mv78xx0, but because Arnd wants a non-DT driver.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-03-18 16:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-17 20:15 [GIT PULL 0/3] ARM: mvebu: changes for v3.10 Jason Cooper
2013-03-17 20:15 ` [GIT PULL 1/3] ARM: mvebu: cleanup " Jason Cooper
2013-03-18 14:50 ` Arnd Bergmann
2013-03-17 20:15 ` [GIT PULL 2/3] ARM: mvebu: drivers " Jason Cooper
2013-03-17 20:15 ` [GIT PULL 3/3] ARM: mvebu: soc " Jason Cooper
2013-03-17 22:26 ` Gregory CLEMENT
2013-03-18 1:07 ` Jason Cooper
2013-03-18 16:18 ` Thomas Petazzoni [this message]
2013-03-18 20:50 ` 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=20130318171824.44814271@skate \
--to=thomas.petazzoni@free-electrons.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).