From: Tony Lindgren <tony@atomide.com>
To: Aaro Koskinen <aaro.koskinen@nokia.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] arm: mach-omap2: n8x0: clean up dummy onenand init
Date: Thu, 2 Dec 2010 17:10:24 -0800 [thread overview]
Message-ID: <20101203011023.GC17222@atomide.com> (raw)
In-Reply-To: <1291305084-9159-1-git-send-email-aaro.koskinen@nokia.com>
* Aaro Koskinen <aaro.koskinen@nokia.com> [101202 07:40]:
> When OneNAND support is disabled, the platform code defines NULL
> board_onenand_data and empty init function for us. By utilizing this we
> can avoid cluttering board files with dummy definitions/wrappers.
Applying these too.
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] arm: mach-omap2: n8x0: clean up dummy onenand init
Date: Thu, 2 Dec 2010 17:10:24 -0800 [thread overview]
Message-ID: <20101203011023.GC17222@atomide.com> (raw)
In-Reply-To: <1291305084-9159-1-git-send-email-aaro.koskinen@nokia.com>
* Aaro Koskinen <aaro.koskinen@nokia.com> [101202 07:40]:
> When OneNAND support is disabled, the platform code defines NULL
> board_onenand_data and empty init function for us. By utilizing this we
> can avoid cluttering board files with dummy definitions/wrappers.
Applying these too.
Tony
next prev parent reply other threads:[~2010-12-03 1:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-02 15:51 [PATCH 1/2] arm: mach-omap2: n8x0: clean up dummy onenand init Aaro Koskinen
2010-12-02 15:51 ` Aaro Koskinen
2010-12-02 15:51 ` [PATCH 2/2] arm: mach-omap2: rx51: " Aaro Koskinen
2010-12-02 15:51 ` Aaro Koskinen
2010-12-03 1:10 ` Tony Lindgren [this message]
2010-12-03 1:10 ` [PATCH 1/2] arm: mach-omap2: n8x0: " Tony Lindgren
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=20101203011023.GC17222@atomide.com \
--to=tony@atomide.com \
--cc=aaro.koskinen@nokia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.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.