From: Scott Wood <oss@buserror.net>
To: Boris Brezillon <boris.brezillon@free-electrons.com>,
Richard Weinberger <richard@nod.at>
Cc: Tom Rini <trini@konsulko.com>, Marek Vasut <marex@denx.de>,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
u-boot@lists.denx.de,
"linux-sunxi@googlegroups.com" <linux-sunxi@googlegroups.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Alexander Kaplan <alex@nextthing.co>,
Brian Norris <computersforpeace@gmail.com>
Subject: Re: [U-Boot] Porting Linux's MTD/NAND changes into U-Boot
Date: Tue, 17 May 2016 23:38:29 -0500 [thread overview]
Message-ID: <1463546309.16584.130.camel@buserror.net> (raw)
In-Reply-To: <20160516140210.746f913d@bbrezillon>
On Mon, 2016-05-16 at 14:02 +0200, Boris Brezillon wrote:
> Hi Scott,
>
> On Tue, 03 May 2016 00:06:45 -0500
> Scott Wood <oss@buserror.net> wrote:
>
> > I usually do syncs when someone complains about needing a sync. Every
> > release
> > seems a bit much. I'll try to do one soon.
>
> Sorry to bother you with that, but can I ask when you plan to do this
> sync (I guess you'll sync with 4.6)? As I explained, I depend on
> features introduced in 4.6 to make the sunxi NAND driver usable on
> sunxi based boards (the concept of data randomizer/scrambler is
> required on some MLC NANDs, and most Allwinner boards embed this
> kind of NAND chips).
>
> Don't hesitate to let me know if you need some help.
I'm working on it now. Yes, with 4.6.
-Scott
next prev parent reply other threads:[~2016-05-18 4:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-25 14:43 Porting Linux's MTD/NAND changes into U-Boot Boris Brezillon
2016-04-25 17:36 ` [U-Boot] " Tom Rini
2016-04-25 20:53 ` Boris Brezillon
2016-05-03 5:06 ` Scott Wood
2016-05-03 7:36 ` Boris Brezillon
2016-05-16 12:02 ` Boris Brezillon
2016-05-18 4:38 ` Scott Wood [this message]
2016-04-26 5:17 ` Heiko Schocher
2016-04-26 7:20 ` Richard Weinberger
2016-04-26 8:13 ` Heiko Schocher
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=1463546309.16584.130.camel@buserror.net \
--to=oss@buserror.net \
--cc=alex@nextthing.co \
--cc=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-sunxi@googlegroups.com \
--cc=marex@denx.de \
--cc=richard@nod.at \
--cc=thomas.petazzoni@free-electrons.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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).