linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: w@1wt.eu (Willy Tarreau)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] Add .dts file for Netgear ReadyNAS 102
Date: Thu, 4 Jul 2013 16:01:16 +0200	[thread overview]
Message-ID: <20130704140116.GD20739@1wt.eu> (raw)
In-Reply-To: <20130704155951.268ebada@skate>

On Thu, Jul 04, 2013 at 03:59:51PM +0200, Thomas Petazzoni wrote:
> Hello guys,
> 
> On Tue, 2 Jul 2013 20:23:12 -0300, Ezequiel Garcia wrote:
> 
> > > Yes and indeed I must say that when I read the driver I found some
> > > similarities with pxa3xx, though it was done differently. I initially
> > > wanted to try to merge them but of course without the spec it's a huge
> > > waste of time, especially considering that this is still in the roadmap
> > > of the Free Electrons guys even though low priority.
> > > 
> > 
> > I wish I could say I'm going to work on this soon but, as Thomas said,
> > we have no idea when/if NAND will be prioritized.
> 
> We've got some news. NAND is back into the list of priorities, Ezequiel
> should restart working on NAND support relatively soon.

Yeah, excellent news! Thanks for keeping us up to date!

Best regards,
Willy

  reply	other threads:[~2013-07-04 14:01 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-30 20:59 [RFC] Add .dts file for Netgear ReadyNAS 102 Arnaud Ebalard
2013-07-02 12:46 ` Jason Cooper
2013-07-02 13:14   ` Thomas Petazzoni
2013-07-02 13:33     ` Jason Cooper
2013-07-02 13:38       ` Thomas Petazzoni
2013-07-02 13:44         ` Jason Cooper
2013-07-02 13:49           ` Willy Tarreau
2013-07-02 14:24             ` Jason Cooper
2013-07-02 17:22           ` Arnaud Ebalard
2013-07-02 17:41             ` Jason Cooper
2013-07-02 21:48               ` Arnaud Ebalard
     [not found]                 ` <20130702220936.GC10215@1wt.eu>
2013-07-02 23:23                   ` Ezequiel Garcia
2013-07-03  4:33                     ` Willy Tarreau
2013-07-03 22:33                       ` Ezequiel Garcia
2013-07-03 22:38                         ` Willy Tarreau
2013-07-03  7:42                     ` Thomas Petazzoni
2013-07-03 13:00                       ` Ezequiel Garcia
2013-07-03 19:07                       ` Willy Tarreau
2013-07-03 19:10                         ` Jason Cooper
2013-07-03 19:38                           ` Willy Tarreau
2013-07-03 19:39                             ` Jason Cooper
2013-07-04 13:59                     ` Thomas Petazzoni
2013-07-04 14:01                       ` Willy Tarreau [this message]
2013-07-04 17:33                       ` Jason Cooper
2013-07-03 20:21                   ` Jason Cooper
2013-07-03 20:35                     ` Willy Tarreau
2013-07-03 20:44                       ` Jason Cooper
2013-07-03 21:14                         ` Willy Tarreau
2013-07-03 22:23                           ` Willy Tarreau
2013-07-03 22:58                             ` Arnaud Ebalard
2013-07-04  6:15                               ` Willy Tarreau
2013-07-03 21:05                       ` Arnaud Ebalard
2013-07-02 17:21   ` Arnaud Ebalard
2013-07-02 17:38     ` Jason Cooper
2013-07-02 13:48 ` Sebastian Hesselbarth
2013-07-02 23:27   ` Arnaud Ebalard

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=20130704140116.GD20739@1wt.eu \
    --to=w@1wt.eu \
    --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).