From: Artem Bityutskiy <dedekind1@gmail.com>
To: John Crispin <blogic@openwrt.org>
Cc: MIPS Mailing List <linux-mips@linux-mips.org>,
MTD Maling List <linux-mtd@lists.infradead.org>
Subject: Re: xway_nand does not build
Date: Tue, 08 May 2012 14:21:47 +0300 [thread overview]
Message-ID: <1336476107.23308.31.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <4FA8FF4C.5050400@openwrt.org>
[-- Attachment #1: Type: text/plain, Size: 1024 bytes --]
On Tue, 2012-05-08 at 13:11 +0200, John Crispin wrote:
> > OK, so I should drop this patch from l2-mtd.git:
> >
> > commit e4445062be41c27b2a0b4f2e1e770d24b68686f4
> > Author: John Crispin <blogic@openwrt.org>
> > Date: Mon Apr 30 19:30:48 2012 +0200
> >
> > mtd: mips: lantiq: add xway nand support
> >
> > Add NAND support on Lantiq XWAY SoC.
> >
> > The driver uses plat_nand. As the platform_device is loaded from DT, we need
> > to lookup the node and attach our xway specific "struct platform_nand_data"
> > to it.
> >
> > Signed-off-by: John Crispin <blogic@openwrt.org>
> > Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
> >
> > Right?
> Hi,
>
> That would be appreciated. i will get aligned with Ralf to make sure
> this patch flow via his tree
OK, dropped. Please, add the OF dependency to the Kconfig yourself then
because I do not have this driver in my tree anymore.
Thanks!
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-05-08 11:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-08 11:00 xway_nand does not build Artem Bityutskiy
2012-05-08 11:01 ` John Crispin
2012-05-08 11:13 ` Artem Bityutskiy
2012-05-08 11:11 ` John Crispin
2012-05-08 11:21 ` Artem Bityutskiy [this message]
2012-05-08 11:22 ` Artem Bityutskiy
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=1336476107.23308.31.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=blogic@openwrt.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-mtd@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.