From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: <xiaolei.li@mediatek.com>
Cc: <computersforpeace@gmail.com>, <dwmw2@infradead.org>,
<linux-mtd@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>, <rogercc.lin@mediatek.com>,
<srv_heupstream@mediatek.com>, <jie.wu@mediatek.com>
Subject: Re: [PATCH] mtd: nand: mtk: change the compile sequence of mtk_nand.o and mtk_ecc.o
Date: Sun, 29 Oct 2017 20:44:11 +0100 [thread overview]
Message-ID: <20171029204411.58e3c3e8@bbrezillon> (raw)
In-Reply-To: <1509173543-38195-1-git-send-email-xiaolei.li@mediatek.com>
On Sat, 28 Oct 2017 14:52:23 +0800
<xiaolei.li@mediatek.com> wrote:
> From: Xiaolei Li <xiaolei.li@mediatek.com>
>
> There will get mtk ecc handler during mtk nand probe now.
> If mtk ecc module is not initialized, then mtk nand probe will return
> -EPROBE_DEFER, and retry later.
>
> Change the compile sequence of mtk_nand.o and mtk_ecc.o, initialize mtk
> ecc module before mtk nand module. This makes mtk nand module initialized
> as soon as possible.
>
Applied.
Thanks,
Boris
> Signed-off-by: Xiaolei Li <xiaolei.li@mediatek.com>
> ---
> drivers/mtd/nand/Makefile | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/mtd/nand/Makefile b/drivers/mtd/nand/Makefile
> index ade5fc4..57f4cde 100644
> --- a/drivers/mtd/nand/Makefile
> +++ b/drivers/mtd/nand/Makefile
> @@ -58,7 +58,7 @@ obj-$(CONFIG_MTD_NAND_SUNXI) += sunxi_nand.o
> obj-$(CONFIG_MTD_NAND_HISI504) += hisi504_nand.o
> obj-$(CONFIG_MTD_NAND_BRCMNAND) += brcmnand/
> obj-$(CONFIG_MTD_NAND_QCOM) += qcom_nandc.o
> -obj-$(CONFIG_MTD_NAND_MTK) += mtk_nand.o mtk_ecc.o
> +obj-$(CONFIG_MTD_NAND_MTK) += mtk_ecc.o mtk_nand.o
>
> nand-objs := nand_base.o nand_bbt.o nand_timings.o nand_ids.o
> nand-objs += nand_amd.o
prev parent reply other threads:[~2017-10-29 19:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-28 6:52 [PATCH] mtd: nand: mtk: change the compile sequence of mtk_nand.o and mtk_ecc.o xiaolei.li
2017-10-29 19:44 ` Boris Brezillon [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=20171029204411.58e3c3e8@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=jie.wu@mediatek.com \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=rogercc.lin@mediatek.com \
--cc=srv_heupstream@mediatek.com \
--cc=xiaolei.li@mediatek.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