From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 3/6] mtd: nand: Add the sunxi NAND controller driver
Date: Mon, 6 Jun 2016 18:22:23 +0200 [thread overview]
Message-ID: <20160606182223.1636b0df@bbrezillon> (raw)
In-Reply-To: <31991e89-53e0-0d9c-c643-241c6f8e8d51@redhat.com>
On Mon, 6 Jun 2016 17:36:10 +0200
Hans de Goede <hdegoede@redhat.com> wrote:
> > +#ifndef CONFIG_SPL_BUILD
> > +void sunxi_nand_init(void);
> > +#endif
> > +
>
> Can we have this in a header somewhere please, and without
> the #ifdef around it, that is not necessary for prototypes.
Hehe, I was expecting this one :-). Do you know where I should put this
prototype definition? A board.h file in board/sunxi/?
--
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-06-06 16:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-06 15:21 [U-Boot] [PATCH 0/6] sunxi: Add NAND controller driver Boris Brezillon
2016-06-06 15:21 ` [U-Boot] [PATCH 1/6] sunxi: Add missing macros to configure the NAND controller clk Boris Brezillon
2016-06-06 15:21 ` [U-Boot] [PATCH 2/6] mtd: nand: add common DT init code Boris Brezillon
2016-06-06 15:21 ` [U-Boot] [PATCH 3/6] mtd: nand: Add the sunxi NAND controller driver Boris Brezillon
2016-06-06 15:36 ` Hans de Goede
2016-06-06 16:22 ` Boris Brezillon [this message]
2016-06-06 17:56 ` Scott Wood
2016-06-06 18:31 ` Boris Brezillon
2016-06-06 23:54 ` Scott Wood
2016-06-07 5:41 ` Boris Brezillon
2016-06-09 0:44 ` Scott Wood
2016-06-06 15:21 ` [U-Boot] [PATCH 4/6] sun5i: Add NAND controller to the sun5i DTSI Boris Brezillon
2016-06-06 15:21 ` [U-Boot] [PATCH 5/6] mtd: nand: Add a full-id entry for the H27QCG8T2E5R‐BCF NAND Boris Brezillon
2016-06-06 15:21 ` [U-Boot] [PATCH 6/6] sunxi: Enable NAND controller on the CHIP Boris Brezillon
2016-06-06 15:37 ` [U-Boot] [linux-sunxi] [PATCH 0/6] sunxi: Add NAND controller driver Hans de Goede
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=20160606182223.1636b0df@bbrezillon \
--to=boris.brezillon@free-electrons.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