From: Brian Norris <computersforpeace@gmail.com>
To: Richard Weinberger <richard.weinberger@gmail.com>
Cc: Zubair Lutfullah Kakakhel <Zubair.Kakakhel@imgtec.com>,
David Woodhouse <dwmw2@infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: [PATCH_V3 0/2] mtd: nand: jz4780: Add nand and bch driver
Date: Fri, 24 Jul 2015 12:34:23 -0700 [thread overview]
Message-ID: <20150724193423.GJ8876@google.com> (raw)
In-Reply-To: <CAFLxGvxsatxukr0ohuWsbm9cgPSkL_aod8527Ue02kY-ksPyqg@mail.gmail.com>
On Wed, Jun 03, 2015 at 11:02:05AM +0200, Richard Weinberger wrote:
> On Wed, Apr 1, 2015 at 11:30 AM, Zubair Lutfullah Kakakhel
> <Zubair.Kakakhel@imgtec.com> wrote:
> > NEMC is going via greg-kh. They went through greg's char-misc-testing and
> > just got applied here.
> >
> > https://git.kernel.org/cgit/linux/kernel/git/gregkh/char-misc.git/log/?h=char-misc-next
> >
> > Do you think that can work for compile testing? It is the upstream tree with nemc.
> >
> > I could point our github ones for the ci20 board.
> > But it has quite a bit of other code too for jz4780 support.
>
> what's the state of this driver? It would be nice to see it upstream.
Status: doesn't build against mainline. Looks like a lot of 'jz47xx...'
names changed to 'jz4780...'. Please resubmit.
Thanks,
Brian
prev parent reply other threads:[~2015-07-24 19:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-31 16:59 Zubair Lutfullah Kakakhel
2015-03-31 16:59 ` [PATCH_V3 1/2] dt-bindings: binding for jz4780-{nand,bch} Zubair Lutfullah Kakakhel
2015-03-31 16:59 ` [PATCH_V3 2/2] mtd: nand: jz4780: driver for NAND devices on JZ4780 SoCs Zubair Lutfullah Kakakhel
2015-03-31 17:20 ` [PATCH_V3 0/2] mtd: nand: jz4780: Add nand and bch driver Brian Norris
2015-04-01 9:30 ` Zubair Lutfullah Kakakhel
2015-06-03 9:02 ` Richard Weinberger
2015-07-24 19:34 ` Brian Norris [this message]
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=20150724193423.GJ8876@google.com \
--to=computersforpeace@gmail.com \
--cc=Zubair.Kakakhel@imgtec.com \
--cc=devicetree@vger.kernel.org \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=richard.weinberger@gmail.com \
/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
Powered by JetHome