From: dinguyen@altera.com (Dinh.Nguyen)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCHv2 0/2]arm: socfpga: Add initial support for Altera's SOCFPGA HW
Date: Tue, 17 Jul 2012 10:46:25 -0600 [thread overview]
Message-ID: <1342543585.13530.3.camel@dinh-ubuntu> (raw)
In-Reply-To: <201207171543.42889.arnd@arndb.de>
On Tue, 2012-07-17 at 15:43 +0000, Arnd Bergmann wrote:
> On Monday 16 July 2012, Pavel Machek wrote:
> > Arnd, do you think this is good enough to go to the next tree? It
> > is new architecture, it should not break anything, I believe we
> > addressed all the issues raised in the review, and noone is reporting
> > new ones.
> >
> > Plus, if we could make initial support into 3.6, that would be very
> > nice :-).
>
> I think we can make it for v3.6, but it's very late for that and I
> haven't looked at it enough in the past. I have a few small
> comments, so if you can address them quickly we can take it.
Hi Arnd. Thanks, please fire away your comments.
Dinh
>
> Arnd
>
next prev parent reply other threads:[~2012-07-17 16:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-12 17:26 [RFC PATCHv2 0/2]arm: socfpga: Add initial support for Altera's SOCFPGA HW dinguyen at altera.com
2012-07-12 17:26 ` [RFC PATCHv2 1/2] ARM: socfpga: initial support for Altera's SOCFPGA platform dinguyen at altera.com
2012-07-16 22:46 ` Rob Herring
2012-07-17 15:47 ` Arnd Bergmann
2012-07-17 21:31 ` Dinh.Nguyen
2012-07-17 21:23 ` Arnd Bergmann
2012-07-12 17:26 ` [RFC PATCHv2 2/2] ARM: socfpga: Add board support for Altera's SOCFPGA Cyclone 5 HW dinguyen at altera.com
2012-07-16 22:43 ` Rob Herring
2012-07-17 7:20 ` Thomas Petazzoni
2012-07-17 7:13 ` Thomas Petazzoni
2012-07-17 15:44 ` Dinh.Nguyen
2012-07-17 15:56 ` Arnd Bergmann
2012-07-16 21:37 ` [RFC PATCHv2 0/2]arm: socfpga: Add initial support for Altera's SOCFPGA HW Pavel Machek
2012-07-17 15:43 ` Arnd Bergmann
2012-07-17 16:46 ` Dinh.Nguyen [this message]
2012-07-18 10:35 ` Pavel Machek
2012-07-18 10:36 ` Pavel Machek
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=1342543585.13530.3.camel@dinh-ubuntu \
--to=dinguyen@altera.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).