From: Jan Weitzel <J.Weitzel@phytec.de>
To: Grazvydas Ignotas <notasas@gmail.com>
Cc: linux-omap@vger.kernel.org, dedekind1@gmail.com,
dedekind@infradead.org, linux-mtd@lists.infradead.org,
tglx@linutronix.de, computersforpeace@gmail.com
Subject: Re: [PATCH] mdt nand: omap2+ use platform options
Date: Mon, 05 Dec 2011 09:11:17 +0100 [thread overview]
Message-ID: <1323072677.12068.5.camel@lws-weitzel> (raw)
In-Reply-To: <CANOLnOOE3a0BP0TcLnRAmq5YAiHLZTpkbriDh9WtkkBT7TotFA@mail.gmail.com>
Am Freitag, den 02.12.2011, 12:20 +0200 schrieb Grazvydas Ignotas:
> On Thu, Dec 1, 2011 at 10:42 AM, Artem Bityutskiy <dedekind1@gmail.com> wrote:
> > On Tue, 2011-11-29 at 10:00 +0100, Jan Weitzel wrote:
> >> Signed-off-by: Jan Weitzel <j.weitzel@phytec.de>
> >
> > Pushed to l2-mtd-2.6.git, thank you!
>
> This breaks build here, did you really test it, Jan?
Sorry, I wasn't carefully enough. I missed 7a559c78 where you removed
options from struct omap_nand_platform_data. Did you think getting we
should reintroduce it? I am looking for a good way to get
NAND_NO_SUBPAGE_WRITE from boardfile to driver.
Jan
> drivers/mtd/nand/omap2.c: In function 'omap_nand_probe':
> drivers/mtd/nand/omap2.c:1078: error: 'struct omap_nand_platform_data'
> has no member named 'options'
>
>
next prev parent reply other threads:[~2011-12-05 8:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-28 14:20 [RFC] mtd/nand: modify NAND_CHIPOPTIONS_MSK Jan Weitzel
2011-11-28 18:34 ` Brian Norris
2011-11-29 9:00 ` [PATCH] mdt nand: omap2+ use platform options Jan Weitzel
2011-11-30 20:31 ` Brian Norris
2011-12-01 8:21 ` Jan Weitzel
2011-12-01 8:42 ` Artem Bityutskiy
2011-12-02 10:20 ` Grazvydas Ignotas
2011-12-02 11:10 ` Artem Bityutskiy
2011-12-02 17:28 ` Brian Norris
2011-12-04 14:29 ` Artem Bityutskiy
2011-12-05 8:11 ` Jan Weitzel [this message]
2011-12-05 10:32 ` Grazvydas Ignotas
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=1323072677.12068.5.camel@lws-weitzel \
--to=j.weitzel@phytec.de \
--cc=computersforpeace@gmail.com \
--cc=dedekind1@gmail.com \
--cc=dedekind@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=notasas@gmail.com \
--cc=tglx@linutronix.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